upower/1.90.2-8build3 autopkgtest failure on arm64

Bug #2060335 reported by Chris Peterson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upower (Ubuntu)
Fix Committed
Undecided
Chris Peterson

Bug Description

autopkgtests fail, only on arm64, after a no-change-rebuild, with the following output:

689s TI:22:39:23 Handling SIGTERM
689s .
689s ======================================================================
689s ERROR: test_daemon_restart (__main__.Tests.test_daemon_restart)
689s ----------------------------------------------------------------------
689s Traceback (most recent call last):
689s File "/usr/lib/python3.12/shutil.py", line 785, in rmtree
689s _rmtree_safe_fd(fd, path, onexc)
689s File "/usr/lib/python3.12/shutil.py", line 717, in _rmtree_safe_fd
689s onexc(os.unlink, fullname, err)
689s File "/usr/lib/python3.12/shutil.py", line 715, in _rmtree_safe_fd
689s os.unlink(entry.name, dir_fd=topfd)
689s FileNotFoundError: [Errno 2] No such file or directory: 'history-time-full-G935_Gaming_Headset.dat.KL0SL2'
689s
689s ======================================================================
689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart)
689s ----------------------------------------------------------------------
689s Traceback (most recent call last):
689s File "/usr/libexec/upower/integration-test.py", line 2558, in test_daemon_restart
689s self.stop_daemon()
689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon
689s self.assertEqual(self.daemon.wait(timeout=5.0), 0)
689s AssertionError: -15 != 0
689s
689s ======================================================================
689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart)
689s ----------------------------------------------------------------------
689s Traceback (most recent call last):
689s File "/usr/libexec/upower/integration-test.py", line 173, in tearDown
689s self.stop_daemon()
689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon
689s self.assertEqual(self.daemon.wait(timeout=5.0), 0)
689s AssertionError: -15 != 0
689s
689s ----------------------------------------------------------------------
689s Ran 66 tests in 194.378s
689s
689s FAILED (failures=2, errors=1)

full log:

https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/u/upower/20240405_224518_5cff1@/log.gz

These test passed in the previous version:
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/u/upower/20240405_224754_d187c@/log.gz

Chris Peterson (cpete)
description: updated
Changed in upower (Ubuntu):
assignee: nobody → Chris Peterson (cpete)
status: New → In Progress
Revision history for this message
Chris Peterson (cpete) wrote :

I estimate another ncr could fix the issue. Building and testing in a ppa.

Revision history for this message
Chris Peterson (cpete) wrote (last edit ):

Yes, a no-change rebuild fixes the issue.

Please see attached debdiff for the fix.

I have provided a PPA with the build and tests:

PPA: https://launchpad.net/~cpete/+archive/ubuntu/upower

arm64 autopkgtest log:

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-cpete-upower/noble/arm64/u/upower/20240407_191552_37f4e@/log.gz

arm64 autopkgtests artifacts:

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-cpete-upower/noble/arm64/u/upower/20240407_191552_37f4e@/artifacts.tar.gz

For transparency: I realized my changelog entry wasn't the most informative. So I modified it post build. i.e. the changelog isn't the same in the ppa.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

At the moment, noble-proposed has https://launchpad.net/ubuntu/+source/upower/1.90.3-1, uploaded a few hours ago:

upower (1.90.3-1) unstable; urgency=medium

  * New upstream version 1.90.3
  * Drop patches, merged upstream
  * Bump Build-Depends on meson to (>= 0.60.0) and libglib2.0-dev to (>= 2.66)
    as per meson.build
  * Switch Build-Depends on pkg-config to pkgconf
  * Bump Standards-Version to 4.7.0

 -- Michael Biebl <email address hidden> Mon, 08 Apr 2024 09:42:45 +0200

According to https://autopkgtest.ubuntu.com/packages/u/upower/noble/arm64 arm64 tests with that version have passed already:
(...)
905s Ran 67 tests in 174.527s
905s
905s OK
905s PASS: upower/upower-integration.test
905s SUMMARY: total=1; passed=1; skipped=0; failed=0; user=11.5s; system=4.9s; maxrss=33304
906s autopkgtest [06:17:15]: test installed-tests: -----------------------]
907s installed-tests PASS

Closing bug (fix committed, since it's not yet in the release pocket).

Changed in upower (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

And unsubscribing sponsors.

Revision history for this message
Chris Peterson (cpete) wrote :

That works! Thanks Andreas.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.