Project

General

Profile

Actions

action #167269

closed

coordination #154768: [saga][epic][ux] State-of-art user experience for openQA

coordination #154771: [epic] Improved test developer user experience

[sporadic] full-stack.t fails - Unexpected Javascript console errors size:S

Added by tinita about 2 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2024-09-24
Due date:
% Done:

0%

Estimated time:

Description

Observation

https://github.com/os-autoinst/openQA/pull/5910
https://app.circleci.com/pipelines/github/os-autoinst/openQA/14687/workflows/5a12e57a-aea7-4f71-9bce-f47809a264c0/jobs/139517

[14:12:34] t/full-stack.t ......... 31/?         # Unexpected Javascript console errors: [
        #   {
        #     level     => "SEVERE",
        #     message   => "http://localhost:9526/tests/Unable%20to%20read%20image:%20Can't%20read%20from%20file%20%22/tmp/webui.worker-1.vWMxweLj/%22:%20Is%20a%20directory%20at%20/home/squamata/project/lib/OpenQA/Shared/Controller/Running.pm%20line%20229. - Failed to load resource: the server responded with a status of 404 (Not Found)",
        #     source    => "network",
        #     timestamp => 1727187304398,
        #   },
        # ]
        # full result panel contents:
        # State: running, started less than a minute ago
        # Scheduled product: job has not been created by posting an ISO
        # Assigned worker: 60cc7dcaf735:1
        # Actions:
        # 
        # Restart job
        #  
        # Cancel job

        #   Failed test 'Expected result not found'
        #   at /home/squamata/project/t/lib/OpenQA/Test/FullstackUtils.pm line 76.

        #   Failed test 'job 5 passed'
        #   at t/full-stack.t line 349.
        # 0

        #   Failed test 'Test 5 result done'
       #   at t/full-stack.t line 356.
...

Acceptance criteria

  • AC1: No errors or unhandled output consistently in t/full-stack.t executions

Suggestions

  • make test STABILITY_TEST=1 RETRY=10 KEEP_DB=1 FULLSTACK=1 TESTS=t/full-stack.t or if you have a test setup prepared and provided the environment variables count-fail-ratio env FULLSTACK=1 prove -l t/full-stack.t
  • Bisect recent commits to find where this problem might have been introduced
Actions #2

Updated by tinita about 2 months ago

  • Subject changed from [sporadic] full-stack.t fails - Failed test 'Expected result not found' to [sporadic] full-stack.t fails - Unexpected Javascript console errors
  • Description updated (diff)
Actions #3

Updated by okurz about 2 months ago

  • Description updated (diff)
Actions #4

Updated by okurz about 2 months ago

  • Subject changed from [sporadic] full-stack.t fails - Unexpected Javascript console errors to [sporadic] full-stack.t fails - Unexpected Javascript console errors size:S
  • Description updated (diff)
  • Status changed from New to Workable
Actions #5

Updated by mkittler about 2 months ago

  • Status changed from Workable to In Progress
  • Assignee set to mkittler
Actions #6

Updated by mkittler about 2 months ago

  • Status changed from In Progress to Feedback
Actions #7

Updated by mkittler about 2 months ago

  • Status changed from Feedback to Resolved

The PR has been merged and after a brief check the issue doesn't seem to occur again.

Actions #8

Updated by okurz about 1 month ago

  • Parent task set to #154771
Actions

Also available in: Atom PDF