Actions
action #67975
closedTest running since 6 hours but not really started
Start date:
2020-06-11
Due date:
% Done:
0%
Estimated time:
Description
Test running since 6 hours but not really started.
Seen on openqa-aarch64 with all tests started after create_hdd_kde
(https://openqa.opensuse.org/tests/1295988):
toolkits_kde
: https://openqa.opensuse.org/tests/1296112extra_tests_on_kde
: https://openqa.opensuse.org/tests/1296111boot_linuxrc
: https://openqa.opensuse.org/tests/1296434
Maybe a problem with the download cache?
Updated by ggardet_arm over 4 years ago
- Description updated (diff)
- Priority changed from Normal to High
Updated by ggardet_arm over 4 years ago
It still happens after a restart:
toolkits_kde
: https://openqa.opensuse.org/tests/1296822extra_tests_on_kde
: https://openqa.opensuse.org/tests/1296823boot_linuxrc
: https://openqa.opensuse.org/tests/1296824
Updated by ggardet_arm over 4 years ago
Only openqa-aarch64
worker is affected. I rescheduled the failing tests on the AWS worker (ip-172-25-5-39), and they were fine:
boot_linuxrc
: https://openqa.opensuse.org/tests/1297093extra_tests_on_kde
: https://openqa.opensuse.org/tests/1297098toolkit_kde
: https://openqa.opensuse.org/tests/1297099
Updated by ggardet_arm over 4 years ago
- Related to action #68131: [cache] Cache service misses requests from workers added
Updated by okurz over 4 years ago
- Category set to Regressions/Crashes
- Status changed from New to Resolved
- Assignee set to okurz
The more immediate problem has been fixed. By what I do not know anymore – also I doubt it was me, I just select an assignee to be the talk-to person if necessary – however we still have #68131 for the more technical low-level issue.
Actions