Failure in integration test in linux bot
See original GitHub issueThe logs
Stack:
Error: Protocol error (Target.createTarget): can't access property "closing", selectedTab is null _setPositionalAttributes@chrome://browser/content/tabbrowser-tabs.js:1123:11
_insertTabAtIndex@chrome://browser/content/tabbrowser.js:3286:25
addTab@chrome://browser/content/tabbrowser.js:2710:16
addTab@chrome://remote/content/shared/TabManager.jsm:24:31
createTarget@chrome://remote/content/cdp/domains/parent/Target.jsm:90:28
execute@chrome://remote/content/cdp/domains/DomainCache.jsm:101:25
execute@chrome://remote/content/cdp/sessions/Session.jsm:64:25
onPacket@chrome://remote/content/cdp/CDPConnection.jsm:248:36
onMessage@chrome://remote/content/server/WebSocketTransport.jsm:89:18
handleEvent@chrome://remote/content/server/WebSocketTransport.jsm:71:14
openPromptSync@resource://gre/modules/Prompter.jsm:1057:17
alert@resource://gre/modules/Prompter.jsm:1329:17
alert@resource://gre/modules/Prompter.jsm:80:7
_displayPrintingError@chrome://global/content/printUtils.js:572:21
My feeling is that something is wrong with the printing test and an alert is generated which blocks following attempts to get the current selected tab (see https://searchfox.org/mozilla-central/source/toolkit/components/printing/content/printUtils.js#572).
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Diagnosing a Linux-only unit test failure
We use both AppVeyor and Travis in CI, and only Travis was failing. There were two failures – one testing the equality operators,...
Read more >Integration test fails all unit tests succeed, whats the conclusion?
First you have to determine where the problems are at. Are your unit tests relevant? This includes: Do they have meaningful asserts?
Read more >How to Fix Flaky Tests - Semaphore CI
Randomly failing tests are the hardest to debug. Here's a framework you can use to fix them and keep your test suite healthy....
Read more >Debugging Failing Tests and Test Pipelines - GitLab
These guidelines are intended to help you to investigate end-to-end test pipeline failures so that they can be properly addressed. This will involve...
Read more >Getting Started With RSocket: Testing Spring Boot Responders
It can take a while to run integration tests, and they can fail for unexpected reasons, like when the network is down. So,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
https://bugzilla.mozilla.org/show_bug.cgi?id=1741698 looks somewhat relevant for us as well, since based on quickly skimming through that one it seems that
print.always_print_silent = true
is now being ignored.I have disabled the test in the PR above for the time being until it’s fixed upstream.