[Bug 2109340] [NEW] Test suite failures: stderr confusion

Julian Andres Klode 2109340 at bugs.launchpad.net
Fri Apr 25 10:22:59 UTC 2025


Public bug reported:

[Impact]
plucky+:

After fixing bug 2109339, tests in plucky fail due to a change in xvfb-
run that now causes stderr to remain on stderr, and hence a Testsuite-
Restriction: allow-stderr needs to be added.

plucky and oracular:
Also there are annoying "TestResult has no addDuration method" warnings that we should be fixing, these are really in nosetests, but let's just disable the warnings using:

PYTHONWARNINGS="ignore:TestResult has no addDuration
method:RuntimeWarning"

so the log is easier to read.

[Test plan]
autopkgtests should succeed after upload, and not show warnings about addDuration missing anymore.

[Where problems could occur]
By allowing stderr we could not see regressions in new warnings, however that is not a regression, the tests did not work before, and when they worked, they were inadvertently rendered to stdout :D

** Affects: update-manager (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: update-manager (Ubuntu Oracular)
     Importance: Undecided
         Status: New

** Affects: update-manager (Ubuntu Plucky)
     Importance: Undecided
         Status: New

** Affects: update-manager (Ubuntu Questing)
     Importance: Undecided
         Status: New

** Also affects: update-manager (Ubuntu Plucky)
   Importance: Undecided
       Status: New

** Also affects: update-manager (Ubuntu Questing)
   Importance: Undecided
       Status: New

** Also affects: update-manager (Ubuntu Oracular)
   Importance: Undecided
       Status: New

** Description changed:

  [Impact]
- After fixing bug 2109339, tests in plucky fail due to a change in xvfb-run that now causes stderr to remain on stderr, and hence a Testsuite-Restriction: allow-stderr needs to be added.
+ plucky+:
+ 
+ After fixing bug 2109339, tests in plucky fail due to a change in xvfb-
+ run that now causes stderr to remain on stderr, and hence a Testsuite-
+ Restriction: allow-stderr needs to be added.
+ 
+ plucky and oracular:
+ Also there are annoying "TestResult has no addDuration method" warnings that we should be fixing, these are really in nosetests, but let's just disable the warnings using:
+ 
+ PYTHONWARNINGS="ignore:TestResult has no addDuration
+ method:RuntimeWarning"
+ 
+ so the log is easier to read.
  
  [Test plan]
- autopkgtests should succeed after upload.
+ autopkgtests should succeed after upload, and not show warnings about addDuration missing anymore.
  
  [Where problems could occur]
  By allowing stderr we could not see regressions in new warnings, however that is not a regression, the tests did not work before, and when they worked, they were inadvertently rendered to stdout :D

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2109340

Title:
  Test suite failures: stderr confusion

Status in update-manager package in Ubuntu:
  New
Status in update-manager source package in Oracular:
  New
Status in update-manager source package in Plucky:
  New
Status in update-manager source package in Questing:
  New

Bug description:
  [Impact]
  plucky+:

  After fixing bug 2109339, tests in plucky fail due to a change in
  xvfb-run that now causes stderr to remain on stderr, and hence a
  Testsuite-Restriction: allow-stderr needs to be added.

  plucky and oracular:
  Also there are annoying "TestResult has no addDuration method" warnings that we should be fixing, these are really in nosetests, but let's just disable the warnings using:

  PYTHONWARNINGS="ignore:TestResult has no addDuration
  method:RuntimeWarning"

  so the log is easier to read.

  [Test plan]
  autopkgtests should succeed after upload, and not show warnings about addDuration missing anymore.

  [Where problems could occur]
  By allowing stderr we could not see regressions in new warnings, however that is not a regression, the tests did not work before, and when they worked, they were inadvertently rendered to stdout :D

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2109340/+subscriptions




More information about the foundations-bugs mailing list