Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1131170 > unrolled thread

Bug#1019707: snapd-glib: flaky autopkgtest, particularly on s390x: Test timed out after 300 seconds

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1019707: snapd-glib: flaky autopkgtest, particularly on s390x: Test timed out after 300 seconds Paul Gevers <elbrus@debian.org> - 2023-01-01 22:20 +0100

#1131170 — Bug#1019707: snapd-glib: flaky autopkgtest, particularly on s390x: Test timed out after 300 seconds

[Multipart message — attachments visible in raw view] — view raw

Hi,

On Tue, 13 Sep 2022 21:10:59 +0200 Paul Gevers <elbrus@debian.org> wrote:
> I looked at the results of the autopkgtest of your package. I noticed 
> that it regularly fails s390x and seems to fail everywhere once in a while.

I had a further look today to try and spot a pattern, but really, all 
the logs I check failed at a different test. And it looks like it 
behaves "weird" before the time out. I.e. it's reporting a lot of lines 
like:
Executing: snapd-glib/test-glib.test

which from my reading of [1] is printed when the test is idle.

I had the idea that maybe this was due to race conditions between 
different tests, but from [2] I gathered that the default is no 
parallelism, and I couldn't spot it being changed.

Therefore I conclude that without the root cause found (I suspect in 
gnome-desktop-testing-runner), it's better to either disable the 
autopkgtest, or mark it as flaky. An alternative could be to disable the 
test-glib and test-qt tests, as they seem to always be involved. I'm not 
sure if the rest is worth it and/or more than superficial.

Paul

[1] 
https://gitlab.gnome.org/GNOME/gnome-desktop-testing/-/blob/master/src/gnome-desktop-testing-runner.c#L766
[2] 
https://manpages.debian.org/testing/gnome-desktop-testing/gnome-desktop-testing-runner.1.en.html



For info, my log:

https://ci.debian.net/data/autopkgtest/testing/s390x/s/snapd-glib/29785580/log.gz
FAIL: snapd-glib-2/test-qt.test (Child process killed by signal 8)
snapd-glib-2/test-glib.test
after /get-system-information/refresh_schedule

https://ci.debian.net/data/autopkgtest/testing/s390x/s/snapd-glib/29782315/log.gz
snapd-glib-2/test-glib.test
after /install/async-failure
snapd-glib-2/test-qt.test
after /list/sync

https://ci.debian.net/data/autopkgtest/testing/s390x/s/snapd-glib/29760350/log.gz
ok 98 /get-interfaces2/only-connected
Executing: snapd-glib-2/test-qt.test

https://ci.debian.net/data/autopkgtest/testing/s390x/s/snapd-glib/29747711/log.gz
ok 36 /get-changes/filter-ready-snap
Executing: snapd-glib-2/test-qt.test
ok 80 /get-assertions/sync
Executing: snapd-glib-2/test-glib.test

https://ci.debian.net/data/autopkgtest/testing/s390x/s/snapd-glib/29706490/log.gz
ok 143 /install/progress
Executing: snapd-glib-2/test-glib.test
ok 113 /find/bad-query
Executing: snapd-glib-2/test-qt.test

https://ci.debian.net/data/autopkgtest/testing/s390x/s/snapd-glib/29541611/log.gz
ok 207 /check-buy/not-logged-in
Executing: snapd-glib-2/test-glib.test

https://ci.debian.net/data/autopkgtest/testing/s390x/s/snapd-glib/29352834/log.gz
ok 27 /login/otp-invalid
Executing: snapd-glib-2/test-qt.test

https://ci.debian.net/data/autopkgtest/testing/s390x/s/snapd-glib/29352833/log.gz
ok 58 /get-snap/classic-confinement
Executing: snapd-glib-2/test-glib.test

https://ci.debian.net/data/autopkgtest/testing/s390x/s/snapd-glib/29290447/log.gz
ok 12 /maintenance/none
Executing: snapd-glib/test-glib.test
ok 41 /list/sync
Executing: snapd-glib/test-qt.test

[toc] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web