Public bug reported:

[Impact]
test-pdiff-usage is somewhat flaky, especially on Debian, this makes it less 
flaky. No end user impact as it's a test-only change.

[Test plan]
Running autopkgtest, which runs our extensive integration test suite which 
includes the changed test.

[Where problems could occur]
No end user regression potential on its own, but might slightly change 
regression potential for future pdiff changes:

Test approach is slightly different now. It still catches that updates
fail correctly, but tests more concretely that a transaction was aborted
rather than that no worker received work (which was not guaranteed, the
work could be scheduled before it was aborted).

** Affects: apt (Ubuntu)
     Importance: Undecided
         Status: Fix Committed

** Affects: apt (Ubuntu Bionic)
     Importance: Undecided
         Status: New

** Affects: apt (Ubuntu Focal)
     Importance: Undecided
         Status: New

** Affects: apt (Ubuntu Groovy)
     Importance: Undecided
         Status: New

** Also affects: apt (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: apt (Ubuntu Groovy)
   Importance: Undecided
       Status: New

** Also affects: apt (Ubuntu Bionic)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1918920

Title:
  Harden test for no new acquires after transaction abort

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Bionic:
  New
Status in apt source package in Focal:
  New
Status in apt source package in Groovy:
  New

Bug description:
  [Impact]
  test-pdiff-usage is somewhat flaky, especially on Debian, this makes it less 
flaky. No end user impact as it's a test-only change.

  [Test plan]
  Running autopkgtest, which runs our extensive integration test suite which 
includes the changed test.

  [Where problems could occur]
  No end user regression potential on its own, but might slightly change 
regression potential for future pdiff changes:

  Test approach is slightly different now. It still catches that updates
  fail correctly, but tests more concretely that a transaction was
  aborted rather than that no worker received work (which was not
  guaranteed, the work could be scheduled before it was aborted).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918920/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to