action #55460: flaky test: t/33-developer_mode.t - not ok 308 - Wait for (?^:\"set_pause_on_screen_mismatch\":\"assert_screen\") timed out - openQA Project - openSUSE Project Management Tool

Actions

Copy link

action #55460

closed

flaky test: t/33-developer_mode.t - not ok 308 - Wait for (?^:\"set_pause_on_screen_mismatch\":\"assert_screen\") timed out

Added by okurz over 4 years ago. Updated about 4 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

okurz

Category:

Regressions/Crashes

Target version:

Done

Start date:

2019-08-13

Due date:

% Done:

Estimated time:

Description

Observation¶

See https://travis-ci.org/os-autoinst/openQA/jobs/571252191#L1404 2/20 test runs:

    not ok 308 - Wait for (?^:\"set_pause_on_screen_mismatch\":\"assert_screen\") timed out
    #   Failed test 'Wait for (?^:\"set_pause_on_screen_mismatch\":\"assert_screen\") timed out'
    #   at /opt/testing_area/openqa/t/lib/OpenQA/Test/FullstackUtils.pm line 160.

Related issues 4 (0 open — 4 closed)

Actions

Copy link

Updated by okurz over 4 years ago

Copied from action #55457: flaky test: t/api/11-bugs.t added

Actions

Copy link

Updated by okurz over 4 years ago

Related to action #53603: unstable test "t/33-developer_mode.t" added

Actions

Copy link

Updated by okurz over 4 years ago

Related to action #53594: travis CI tests fail on master in t/33-developer_mode.t "owned by Demo (2 minutes ago, developer has 3 tabs open)' doesn't match '(?^:owned by Demo.*2 tabs open)" added

Actions

Copy link

Updated by okurz over 4 years ago

Related to action #37638: Flaky fullstack test: 'Test 3 is scheduled' at t/full-stack.t added

Actions

Copy link

Updated by mkittler over 4 years ago

According to the log the command set_pause_on_screen_mismatch has been sent and no disconnects happened at this time. Hence this should have worked. However, the response is really missing. So this is maybe even flaky behavior of the command processing itself and not only a flaky test.

Actions

Copy link