diff options
author | toofar <toofar@spalge.com> | 2023-11-19 20:53:37 +1300 |
---|---|---|
committer | toofar <toofar@spalge.com> | 2023-11-24 21:47:01 +1300 |
commit | b643e7b411a9bb4eae47b2e3a22442cc6d6f5088 (patch) | |
tree | ea9adb1e5906c4fb5dcf71257ad84c248c8d8988 | |
parent | bd865777368018774760f6fa81cf3b582104acda (diff) | |
download | qutebrowser-b643e7b411a9bb4eae47b2e3a22442cc6d6f5088.tar.gz qutebrowser-b643e7b411a9bb4eae47b2e3a22442cc6d6f5088.zip |
Try getting sandbox page text again
On CI now the sandbox test is failing on windows when we pop the header
line with an index error. It looks like the only line present on the
page is "Sandbox Status". It was working on CI the other day! Grrr
Hopefully it's a timing issue and the JS just hasn't finished running
yet? Not sure if just loading it again is the most reliable. Ideally we
would be listening for some event...
Pretty low effort but if this makes the test stop being flaky and we
don't have to look at it again that's fine with me.
-rw-r--r-- | tests/end2end/test_invocations.py | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/tests/end2end/test_invocations.py b/tests/end2end/test_invocations.py index 72e08af96..a55efb129 100644 --- a/tests/end2end/test_invocations.py +++ b/tests/end2end/test_invocations.py @@ -883,6 +883,11 @@ def test_sandboxing( line.expected = True pytest.skip("chrome://sandbox/ not supported") + if len(text.split("\n")) == 1: + # Try again, maybe the JS hasn't run yet? + text = quteproc_new.get_content() + print(text) + bpf_text = "Seccomp-BPF sandbox" yama_text = "Ptrace Protection with Yama LSM" |