action #52997
closed[sle][functional][tools]test fails in sshd - timeout_exceeded (13:20 hours)
0%
Description
this job has status timeout_exceeded (13:20 hours)
I checked settings, there is no MAX_JOB_TIME.
I found in log about:
[2019-06-13T13:25:24.249 CEST] [debug] isotovideo: unable to inform websocket clients about stopping command server: Connection refused at /usr/bin/isotovideo line 172.
Even the test failed, it should not take so long time.
Observation¶
openQA test in scenario sle-12-SP5-Server-DVD-s390x-system_performance@s390x-kvm-sle12 fails in
sshd
Test suite description¶
Maintainer: okurz@suse.de An explicit system performance test. https://progress.opensuse.org/issues/36100
Reproducible¶
Fails since (at least) Build 0116
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by okurz over 5 years ago
@zluo IMHO a tag "[functional]" without "[u]" or "[y]" should be avoided because there is no team assigned. But I guess you mean for this to be an openQA issue in general anyway, right? If the case I suggest to move to the parent issue tracker.
Updated by zluo over 5 years ago
- Project changed from openQA Tests (public) to openQA Project (public)
- Category deleted (
Bugs in existing tests)
@okurz yes, this is an issue in general.
Updated by okurz over 5 years ago
- Is duplicate of action #47087: [scheduling] Workers on openqaworker2 stuck frequently added
Updated by okurz over 5 years ago
- Category set to Regressions/Crashes
- Status changed from New to Rejected
- Assignee set to okurz
ok, we have enough of tickets for "worker stuck" though so handling as duplicate of existing entry #47087
Updated by okurz over 4 years ago
- Related to coordination #65118: [epic] multimachine test fails with symptoms "websocket refusing connection" and other unclear reasons added