QA » openQA Project

It has failed again on https://github.com/os-autoinst/openQA/pull/5173:

#   at t/ui/15-comments.t line 485.
executeScript: unexpected alert open: {Alert text : The comment text mustn't be empty.} at /home/squamata/project/t/ui/../lib/OpenQA/SeleniumTest.pm:81 at /home/squamata/project/t/ui/../lib/OpenQA/SeleniumTest.pm line 84.
    OpenQA::SeleniumTest::__ANON__(Test::Selenium::Chrome=HASH(0x558a9dda61c0), "Error while executing command: executeScript: unexpected aler"..., HASH(0x558a9e43ad80), HASH(0x558a9e438bd0)) called at /usr/lib/perl5/vendor_perl/5.26.1/Selenium/Remote/Driver.pm line 356
    Selenium::Remote::Driver::catch {...} ("Error while executing command: executeScript: unexpected aler"...) called at /usr/lib/perl5/vendor_perl/5.26.1/Try/Tiny.pm line 123
    Try::Tiny::try(CODE(0x558a9e4356d8), Try::Tiny::Catch=REF(0x558a9e445070)) called at /usr/lib/perl5/vendor_perl/5.26.1/Selenium/Remote/Driver.pm line 361
    Selenium::Remote::Driver::__ANON__(CODE(0x558a9d8e5ee8), Test::Selenium::Chrome=HASH(0x558a9dda61c0), HASH(0x558a9e43ad80), HASH(0x558a9e438bd0)) called at (eval 1713)[/usr/lib/perl5/vendor_perl/5.26.1/Class/Method/Modifiers.pm:89] line 1
    Selenium::Remote::Driver::__ANON__(Test::Selenium::Chrome=HASH(0x558a9dda61c0), HASH(0x558a9e43ad80), HASH(0x558a9e438bd0)) called at (eval 1715)[/usr/lib/perl5/vendor_perl/5.26.1/Class/Method/Modifiers.pm:148] line 2
    Selenium::Remote::Driver::_execute_command(Test::Selenium::Chrome=HASH(0x558a9dda61c0), HASH(0x558a9e43ad80), HASH(0x558a9e438bd0)) called at /usr/lib/perl5/vendor_perl/5.26.1/Selenium/Remote/Driver.pm line 1053
    Selenium::Remote::Driver::execute_script(Test::Selenium::Chrome=HASH(0x558a9dda61c0), "return window.jQuery \x{26}\x{26} jQuery.active === 0") called at /home/squamata/project/t/ui/../lib/OpenQA/SeleniumTest.pm line 163
    OpenQA::SeleniumTest::wait_for_ajax("msg", "comment with pinning for group added by regular user") called at t/ui/15-comments.t line 74
    main::write_comment("pinned-description ... The description", "comment with pinning for group added by regular user") called at t/ui/15-comments.t line 471
    main::__ANON__() called at /usr/lib/perl5/5.26.1/Test/Builder.pm line 309
    eval {...} called at /usr/lib/perl5/5.26.1/Test/Builder.pm line 309
    Test::Builder::subtest(Test::Builder=HASH(0x558a91671d28), "group overview: /parent_group_overview/1", CODE(0x558a9e279d90)) called at /usr/lib/perl5/5.26.1/Test/More.pm line 807
    Test::More::subtest("group overview: /parent_group_overview/1", CODE(0x558a9e279d90)) called at t/ui/15-comments.t line 484
    main::__ANON__() called at /usr/lib/perl5/5.26.1/Test/Builder.pm line 309
    eval {...} called at /usr/lib/perl5/5.26.1/Test/Builder.pm line 309
    Test::Builder::subtest(Test::Builder=HASH(0x558a91671d28), "editing when logged in as regular user", CODE(0x558a9e23c6f0)) called at /usr/lib/perl5/5.26.1/Test/More.pm line 807
    Test::More::subtest("editing when logged in as regular user", CODE(0x558a9e23c6f0)) called at t/ui/15-comments.t line 485
[10:25:40] t/ui/15-comments.t ......................... 13/? # Tests were run but no plan was declared and done_testing() was not seen.

This PR has already been rebased on https://github.com/os-autoinst/openQA/pull/5168 so it is safe to say that the previous use of jQuery was not the culprit.

Note that this trace is slightly different as it happened on a parent group page (and not a normal group page). So the concrete page definitely doesn't make a difference.

If I remove send_keys in write_comment then wait_until indeed waits as expected (and eventually times out). So the waiting condition is definitely correct.

If I add another textarea with the same ID on the page before (e.g. <textarea id="text"></textarea>) I can provoke the problem we see on CircleCI locally. Another textarea with the same name in the same form provokes it as well (e.g. <textarea name="text"></textarea>). Maybe under some conditions such an element is rendered accidentally?

PR to answer that question (and possibly fix the issue): https://github.com/os-autoinst/openQA/pull/5176

mkittler wrote:

If I add another textarea with the same ID on the page before (e.g. <textarea id="text"></textarea>) I can provoke the problem we see on CircleCI locally. Another textarea with the same name in the same form provokes it as well (e.g. <textarea name="text"></textarea>). Maybe under some conditions such an element is rendered accidentally?

I took a brief look at comment_row.html.ep thinking maybe the condition deciding that a row contains the form is flawed. Apparently I don't understand how that works. It looks to me like we should have a form for each comment plus the extra row. I don't see a condition preventing that. Maybe that helps?

The PR has been merged. Let's see how it affects the stability of this test.

I took a brief look at comment_row.html.ep thinking maybe the condition deciding that a row contains the form is flawed. Apparently I don't understand how that works. It looks to me like we should have a form for each comment plus the extra row. I don't see a condition preventing that. Maybe that helps?

I don't think this code is the problem. We always render the editing buttons, the heading, the comment text as rendered markdown and a text area for updating with raw markdown. The text area is hidden by default and only shown when clicking the "Edit" button. So that's ok and this text area only has the name text (and not the id).

Observed again in https://github.com/os-autoinst/openQA/pull/5185 which has already been based on https://github.com/os-autoinst/openQA/pull/5176:

[15:05:50] t/ui/15-comments.t ......................... 12/? 
#   Failed test 'editing when logged in as regular user'
#   at t/ui/15-comments.t line 488.
executeScript: unexpected alert open: {Alert text : The comment text mustn't be empty.} at /home/squamata/project/t/ui/../lib/OpenQA/SeleniumTest.pm:81 at /home/squamata/project/t/ui/../lib/OpenQA/SeleniumTest.pm line 84.
    OpenQA::SeleniumTest::__ANON__(Test::Selenium::Chrome=HASH(0x559c985eaf78), "Error while executing command: executeScript: unexpected aler"..., HASH(0x559c98c800a0), HASH(0x559c98c80310)) called at /usr/lib/perl5/vendor_perl/5.26.1/Selenium/Remote/Driver.pm line 356
    Selenium::Remote::Driver::catch {...} ("Error while executing command: executeScript: unexpected aler"...) called at /usr/lib/perl5/vendor_perl/5.26.1/Try/Tiny.pm line 123
    Try::Tiny::try(CODE(0x559c98c7d398), Try::Tiny::Catch=REF(0x559c98c8cdf0)) called at /usr/lib/perl5/vendor_perl/5.26.1/Selenium/Remote/Driver.pm line 361
    Selenium::Remote::Driver::__ANON__(CODE(0x559c983686c8), Test::Selenium::Chrome=HASH(0x559c985eaf78), HASH(0x559c98c800a0), HASH(0x559c98c80310)) called at (eval 1718)[/usr/lib/perl5/vendor_perl/5.26.1/Class/Method/Modifiers.pm:89] line 1
    Selenium::Remote::Driver::__ANON__(Test::Selenium::Chrome=HASH(0x559c985eaf78), HASH(0x559c98c800a0), HASH(0x559c98c80310)) called at (eval 1720)[/usr/lib/perl5/vendor_perl/5.26.1/Class/Method/Modifiers.pm:148] line 2
    Selenium::Remote::Driver::_execute_command(Test::Selenium::Chrome=HASH(0x559c985eaf78), HASH(0x559c98c800a0), HASH(0x559c98c80310)) called at /usr/lib/perl5/vendor_perl/5.26.1/Selenium/Remote/Driver.pm line 1053
    Selenium::Remote::Driver::execute_script(Test::Selenium::Chrome=HASH(0x559c985eaf78), "return window.jQuery \x{26}\x{26} jQuery.active === 0") called at /home/squamata/project/t/ui/../lib/OpenQA/SeleniumTest.pm line 163
    OpenQA::SeleniumTest::wait_for_ajax("msg", "comment with pinning for group added by regular user") called at t/ui/15-comments.t line 77
    main::write_comment("pinned-description ... The description", "comment with pinning for group added by regular user") called at t/ui/15-comments.t line 474
    main::__ANON__() called at /usr/lib/perl5/5.26.1/Test/Builder.pm line 309
    eval {...} called at /usr/lib/perl5/5.26.1/Test/Builder.pm line 309
    Test::Builder::subtest(Test::Builder=HASH(0x559c8bed1c90), "group overview: /parent_group_overview/1", CODE(0x559c98a87c30)) called at /usr/lib/perl5/5.26.1/Test/More.pm line 807
    Test::More::subtest("group overview: /parent_group_overview/1", CODE(0x559c98a87c30)) called at t/ui/15-comments.t line 487
    main::__ANON__() called at /usr/lib/perl5/5.26.1/Test/Builder.pm line 309
    eval {...} called at /usr/lib/perl5/5.26.1/Test/Builder.pm line 309
    Test::Builder::subtest(Test::Builder=HASH(0x559c8bed1c90), "editing when logged in as regular user", CODE(0x559c98a87588)) called at /usr/lib/perl5/5.26.1/Test/More.pm line 807
    Test::More::subtest("editing when logged in as regular user", CODE(0x559c98a87588)) called at t/ui/15-comments.t line 488
[15:05:50] t/ui/15-comments.t ......................... 13/? # Tests were run but no plan was declared and done_testing() was not seen.
                                                              [15:05:50] t/ui/15-comments.t ......................... Dubious, test returned 1 (wstat 256, 0x100)

So this is definitely not about having two elements with the same ID on the page.

Since I'm out of ideas I'm just adding a retry now: https://github.com/os-autoinst/openQA/pull/5188