Open Bug 1857144 Opened 2 years ago Updated 8 months ago

Intermittent /print/crashtests/reload-crash.html | single tracking bug

Categories

(Testing :: web-platform-tests, defect, P5)

defect

Tracking

(Not tracked)

People

(Reporter: intermittent-bug-filer, Unassigned, NeedInfo)

Details

(Keywords: intermittent-failure, intermittent-testcase)

Attachments

(1 obsolete file)

Filed by: ctuns [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=431402533&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/RNT3gmXgQHuk5cF-S99iJA/runs/0/artifacts/public/logs/live_backing.log


[task 2023-10-05T04:59:38.589Z] 04:59:38     INFO - TEST-START | /print/crashtests/reload-crash.html
[task 2023-10-05T04:59:39.158Z] 04:59:39     INFO - TEST-UNEXPECTED-ERROR | /print/crashtests/reload-crash.html | Document unloaded; maybe test navigated the top-level-browsing context?
[task 2023-10-05T04:59:39.158Z] 04:59:39     INFO - TEST-INFO took 569ms
[task 2023-10-05T04:59:39.159Z] 04:59:39     INFO - Restarting browser for new test group
[task 2023-10-05T04:59:39.596Z] 04:59:39     INFO - STDOUT: cleanup aborted: Unable to remount device
[task 2023-10-05T04:59:39.693Z] 04:59:39     INFO - Closing logging queue
[task 2023-10-05T04:59:39.694Z] 04:59:39     INFO - queue closed
[task 2023-10-05T04:59:39.694Z] 04:59:39     INFO - STDOUT: cleanup aborted: Unable to remount device
[task 2023-10-05T04:59:39.711Z] 04:59:39     INFO - Setting up ssl
[task 2023-10-05T04:59:39.727Z] 04:59:39     INFO - certutil | b''
[task 2023-10-05T04:59:39.746Z] 04:59:39     INFO - certutil | b''
[task 2023-10-05T04:59:39.757Z] 04:59:39     INFO - certutil | b'\nCertificate Nickname                                         Trust Attributes\n                                                             SSL,S/MIME,JAR/XPI\n\nweb-platform-tests                                           CT,, \n'
[task 2023-10-05T04:59:40.369Z] 04:59:40     INFO - adb Granting important runtime permissions to org.mozilla.geckoview.test_runner
[task 2023-10-05T04:59:41.596Z] 04:59:41     INFO - adb launch_application: am start -W -n org.mozilla.geckoview.test_runner/org.mozilla.geckoview.test_runner.TestRunnerActivity -a android.intent.action.MAIN --es env0 MOZ_CRASHREPORTER=1 --es env1 MOZ_CRASHREPORTER_NO_REPORT=1 --es env2 MOZ_CRASHREPORTER_SHUTDOWN=1 --es env3 MOZ_HIDE_RESULTS_TABLE=1 --es env4 MOZ_IN_AUTOMATION=1 --es env5 MOZ_LOG=signaling:3,mtransport:4,DataChannel:4,jsep:4 --es env6 R_LOG_LEVEL=6 --es env7 R_LOG_DESTINATION=stderr --es env8 R_LOG_VERBOSE=1 --es env9 MOZ_PROCESS_LOG=/tmp/tmpp49x398ppidlog --es env10 MOZ_DISABLE_NONLOCAL_CONNECTIONS=1 --es arg0 -no-remote --es arg1 -profile --es arg2 /data/local/tmp/test_root/profile --es arg3 --marionette --es arg4 about:blank --ez use_multiprocess True
[task 2023-10-05T04:59:42.759Z] 04:59:42     INFO - Starting runner
[task 2023-10-05T04:59:45.507Z] 04:59:45     INFO - TEST-START | /quirks/crashtests/list-item-whole-line-quirks-crash.html

The test-failure-text here comes from this marionette code:
https://searchfox.org/mozilla-central/rev/41edcdf7fe44678c5913a603a286b1fc3979d540/testing/web-platform/tests/tools/wptrunner/wptrunner/executors/executormarionette.py#894-896

except Exception as e:
    if isinstance(e, errors.JavascriptException) and str(e).startswith("Document was unloaded"):
        message = "Document unloaded; maybe test navigated the top-level-browsing context?"

RE the "maybe test navigated" situation that marionette is alluding to here: in fact I think that's exactly what the test does. The test sets window.location.href here:
https://searchfox.org/mozilla-central/rev/41edcdf7fe44678c5913a603a286b1fc3979d540/testing/web-platform/tests/print/crashtests/reload-crash.html#15-16

var updatedUrl = url + '?isFirstLoad=false';
window.location.href = updatedUrl;

...and per MDN, "Setting the value of href navigates to the provided URL".

jgraham, is the exception indicating that this sort of navigation is disallowed for WPT tests? (If so, perhaps we should file a Chromium bug to get the test fixed; and in the meantime, we can annotate it as skipped-on-Android since that's where this intermittent is happening. I wonder why this is android-specific; maybe the test just gets treated as complete before the setTimeout-based navigation happens on other platforms, since the test doesn't use test-wait.)

Flags: needinfo?(james)
Attachment #9383946 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: