Public bug reported:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy/groovy/armhf/g/glibc/20200910_181049_40237@/log.gz
...
FAIL: time/tst-cpuclock1
original exit status 1
live PID 30062 clock fffc548a resolution 0.000000001
live PID 30062 before sleep => 0.000000000
live PID 30062 after sleep => 0.436834440
before - after 0.436834440 outside reasonable range
dead PID 30062 => 0.551789800
clock_gettime on reaped PID 30062 clock fffc548a => Invalid argument
clock_getres on reaped PID 30062 clock fffc548a => Invalid argument
----------
+---------------------------------------------------------------------+
| Encountered regressions that don't match expected failures. |
+---------------------------------------------------------------------+
FAIL: time/tst-cpuclock1
...
This seems to be a result of the testbeds being overloaded, so XFAIL-ing
for now.
** Affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
** Description changed:
+
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
+ /autopkgtest-groovy/groovy/armhf/g/glibc/20200910_181049_40237@/log.gz
+
...
FAIL: time/tst-cpuclock1
original exit status 1
- live PID 26729 clock fffcbcb2 resolution 0.000000001
- live PID 26729 before sleep => 0.000000000
- live PID 26729 after sleep => 0.427549200
- before - after 0.427549200 outside reasonable range
- dead PID 26729 => 0.534141800
- clock_gettime on reaped PID 26729 clock fffcbcb2 => Invalid argument
- clock_getres on reaped PID 26729 clock fffcbcb2 => Invalid argument
+ live PID 30062 clock fffc548a resolution 0.000000001
+ live PID 30062 before sleep => 0.000000000
+ live PID 30062 after sleep => 0.436834440
+ before - after 0.436834440 outside reasonable range
+ dead PID 30062 => 0.551789800
+ clock_gettime on reaped PID 30062 clock fffc548a => Invalid argument
+ clock_getres on reaped PID 30062 clock fffc548a => Invalid argument
----------
+---------------------------------------------------------------------+
| Encountered regressions that don't match expected failures. |
+---------------------------------------------------------------------+
FAIL: time/tst-cpuclock1
...
This seems to be a result of the testbeds being overloaded, so XFAIL-ing
for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895687
Title:
tst-cpuclock1 test is sometimes failing in on armhf testbefs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1895687/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
