Project

General

Profile

action #55460

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

Added by okurz 10 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Concrete Bugs
Target version:
Start date:
2019-08-13
Due date:
% Done:

0%

Estimated time:
Difficulty:
Duration:

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

Related to openQA Project - action #53603: unstable test "t/33-developer_mode.t"Resolved2019-07-01

Related to openQA Project - 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)"Resolved2019-07-01

Related to openQA Project - action #37638: Flaky fullstack test: 'Test 3 is scheduled' at t/full-stack.tWorkable2018-06-21

Copied from openQA Project - action #55457: flaky test: t/api/11-bugs.tResolved2019-08-13

History

#1 Updated by okurz 10 months ago

#2 Updated by okurz 10 months ago

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

#3 Updated by okurz 10 months 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

#4 Updated by okurz 10 months ago

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

#5 Updated by mkittler 9 months 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.

#6 Updated by okurz 4 months ago

  • Status changed from New to Feedback
  • Assignee set to okurz

#7 Updated by okurz 4 months ago

  • Status changed from Feedback to Resolved
  • Target version set to Done

Also available in: Atom PDF