Project

General

Profile

Actions

action #165764

closed

[ci] t/full-stack.t failing since 2024-08-23

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

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

0%

Estimated time:

Description

Observation

the fullstack tests in circleci and github workflow started failing always this morning:

https://app.circleci.com/pipelines/github/os-autoinst/openQA/14431/workflows/a664b90e-1460-4e34-a3c7-8f79388bbfde/jobs/136686

[11:11:57] t/full-stack.t ......... 16/?     # Unexpected Javascript console errors, waiting for connection opened: [
    #   {
    #     level     => "WARNING",
    #     message   => "http://localhost:9526/asset/e8e9747263/test_result.js 139 A code tag was parsed inside of a <select> which was not inserted into the document. This is not valid HTML and the behavior may be changed in future versions of chrome.",
    #     source    => "javascript",
    #     timestamp => 1724411541729,
    #   },
    #   {
    #     level     => "WARNING",
    #     message   => "http://localhost:9526/asset/e8e9747263/test_result.js 139 A code tag was parsed inside of a <select> which was not inserted into the document. This is not valid HTML and the behavior may be changed in future versions of chrome.",
    #     source    => "javascript",
    #     timestamp => 1724411541729,
    #   },
    #   {
    #     level     => "WARNING",
    #     message   => "http://localhost:9526/asset/e8e9747263/test_result.js 139 A code tag was parsed inside of a <select> which was not inserted into the document. This is not valid HTML and the behavior may be changed in future versions of chrome.",
    #     source    => "javascript",
    #     timestamp => 1724411541729,
    #   },
    # ]

    #   Failed test 'No unexpected js warnings'
    #   at /home/squamata/project/t/lib/OpenQA/Test/FullstackUtils.pm line 123.
    # Looks like you failed 1 test of 2.

#   Failed test 'wait until developer console becomes available'
#   at t/full-stack.t line 196.
[11:11:57] t/full-stack.t ......... 19/?     # Unexpected Javascript console errors: [
    # Cancel job

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

    #   Failed test 'job 1 passed'
    #   at t/full-stack.t line 209.
    # 0

    #   Failed test 'autoinst log uploaded'
    #   at t/full-stack.t line 215.
    #                   '[2024-08-23T11:12:19.216634Z] [debug] [pid:510] Preparing Mojo::IOLoop::ReadWriteProcess::Session
...

https://github.com/os-autoinst/os-autoinst/actions/runs/10524726213/job/29162048661?pr=2539


Related issues 1 (0 open1 closed)

Related to openQA Project - action #164239: full-stack.t failing with "executeScript: unknown error: session deleted because of page crash at t/lib/OpenQA/SeleniumTest.pm:78"Resolvedtinita2024-07-20

Actions
Actions #1

Updated by tinita about 1 month ago

  • Description updated (diff)
Actions #2

Updated by tinita about 1 month ago

  • Related to action #164239: full-stack.t failing with "executeScript: unknown error: session deleted because of page crash at t/lib/OpenQA/SeleniumTest.pm:78" added
Actions #3

Updated by mkittler about 1 month ago

  • Status changed from New to In Progress
  • Assignee set to mkittler
Actions #4

Updated by mkittler about 1 month ago

Maybe due to https://github.com/os-autoinst/os-autoinst/pull/2538. Last time the container was built was 7 days ago. So I now re-triggered the build. Maybe that helps.

Actions #5

Updated by tinita about 1 month ago

We have chromium 128: https://github.com/perlpunk/os-autoinst/actions/runs/10525775151/job/29165241348#step:7:21

The downgrade only happened if we had chromium 126, and in the last CI runs I didn't see the downgrade anymore, that's why I was sure we had the new version.
But to confirm I ran the above commit.

It must be a new bug.

Actions #6

Updated by mkittler about 1 month ago · Edited

There are also more problematic log lines and openQA is also affected:

    # [2024-08-23T12:44:54.089744Z] [debug] [pid:676] Uploading artefact assert_screen-2.png as 68d7ac83452b72555f8a6b386629f91f
    # [2024-08-23T12:44:54.151047Z] [debug] [pid:510] Upload concluded (up to shutdown)
    # '
    #     doesn't match '(?^u:core-hdd\.qcow2: local upload \(no chunks needed\))'

    #   Failed test 'image of hdd uploaded'
    #   at t/full-stack.t line 217.

    #   Failed test 'can stat /home/squamata/project/test-results/fullstack/full-stack.d/openqa/share/factory/hdd/core-hdd.qcow2'
    #   at t/full-stack.t line 220.
Use of uninitialized value in subroutine entry at t/full-stack.t line 221.

    #   Failed test 'exported image has correct permissions (420 -> 0644)'
    #   at t/full-stack.t line 221.
    #          got: '0'
    #     expected: '420'
    # Looks like you failed 8 tests of 14.
[12:44:10] t/full-stack.t ......... 20/?

Those are the lines as of line 218 and I have no idea why we get that Use of uninitialized value … here:

    ok -s path($sharedir, 'factory', 'hdd')->make_path->child('core-hdd.qcow2'), 'image of hdd uploaded';
    my $core_hdd_path = path($sharedir, 'factory', 'hdd')->child('core-hdd.qcow2');
    my @core_hdd_stat = stat($core_hdd_path);
    ok @core_hdd_stat, 'can stat ' . $core_hdd_path;
    is S_IMODE($core_hdd_stat[2]), 420, 'exported image has correct permissions (420 -> 0644)';

It is not just my branch because the same is happening on os-autoinst checks as well.


Probably the problem is just that $core_hdd_stat[2] is undef because the file doesn't exist. However, I couldn't reproduce the problem locally where I also don't see the Chromium-related warnings mentioned in the ticket description.

Actions #7

Updated by mkittler about 1 month ago

Looks like other projects ran into the same problem yesterday: https://github.com/OrchardCMS/OrchardCore/issues/16606

So probably a new warning. I'll try fixing the HTML because we probably have invalid HTML, indeed. If it doesn't work I can still make our tests ignore the warning.

Actions #8

Updated by openqa_review about 1 month ago

  • Due date set to 2024-09-07

Setting due date based on mean cycle time of SUSE QE Tools

Actions #9

Updated by mkittler about 1 month ago

  • Status changed from In Progress to Resolved

It works again after https://github.com/os-autoinst/openQA/pull/5889 has been merged on openQA and os-autoinst.

Actions

Also available in: Atom PDF