[tools] when needle does not exist, test is paused until MAX_JOB_TIME
Test should not be paused  when the needle does not exist, jobs is then hanging (in this case 3 hours) until timeout_exceeded.
[2020-08-12T13:21:39.887 CEST] [debug] <<< testapi::check_screen(mustmatch="yast2-lan-really", timeout=3) [37m[2020-08-12T13:21:39.888 CEST] [debug] NO matching needles for yast2-lan-really [0m[37m[2020-08-12T13:21:40.165 CEST] [debug] no match: 2.7s [0m[37m[2020-08-12T13:21:41.166 CEST] [debug] no match: 1.7s [0m[37m[2020-08-12T13:21:42.167 CEST] [debug] no match: 0.7s [0m[37m[2020-08-12T13:21:43.168 CEST] [debug] no match: -0.3s [0m[32m[2020-08-12T13:21:43.343 CEST] [debug] >>> testapi::_check_backend_response: match=yast2-lan-really timed out after 3 (check_screen) [0m[37m[2020-08-12T13:21:43.365 CEST] [debug] isotovideo: pausing test execution on timeout as requested at console-yast2_lan [0m[37m[37m[37m[2020-08-12T16:24:26.117 CEST] [debug] autotest received signal TERM, saving results of current test before exiting [2020-08-12T16:24:26.117 CEST] [debug] isotovideo received signal TERM [0m[0m[2020-08-12T16:24:26.118 CEST] [debug] backend got TERM
openQA test in scenario sle-15-SP2-Desktop-DVD-Incidents-x86_64-qam-allpatterns@64bit fails in
Test suite description¶
Default system config with all patterns enabled.
Due changes in autoyast profile size of HDD incerased to 40GB
Fails since (at least) Build :16068:freerdp
Last good: :16063:emacs (or more recent)
Always latest result in this scenario: latest
- Project changed from openQA Tests to openQA Project
- Category changed from Bugs in existing tests to Concrete Bugs
- Status changed from New to Rejected
- Assignee set to okurz
- Target version set to Ready
Hi dzedro , I saw you added the "[tools]" keyword in the ticket. We within the SUSE QA Tools team struggle a bit to review tickets with this keyword as we primarily look into the project progress.opensuse.org/projects/openqav3/ .
If this really is the case then it's certainly unexpected behaviour. From the log it looks like that the test was paused from the developer mode or with a setting PAUSE_AT. The full job does not exist anymore unfortunately so I can't check vars.json as well. Later jobs in this scenario do look fine however. Please report back if you see this again.