Bug 1717050 Comment 1 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Revision 1 by
on 
@bomsy: It is possible that `devtools/client/netmonitor/test/browser_net_cause_source_map.js` fails from the same reason? (i.e. different order of resources of various types due to batching)
Revision 2 by
on 
@bomsy: It is possible that `devtools/client/netmonitor/test/browser_net_cause_source_map.js` fails from the same reason? (i.e. different order of resources of various types due to batching)

Here is a list of tests that are failing on timeout since waiting for payloadReady that never happens.
Perhaps there could be common underlying issue

* devtools/client/netmonitor/test/browser_net_cause_source_map.js
* devtools/client/netmonitor/test/browser_net_initiator.js (this one)
* devtools/client/netmonitor/test/browser_net_websocket_stacks.js
* devtools/client/netmonitor/test/browser_net_worker_stacks.js

Honza
Revision 3 by
on 
@bomsy: It is possible that `devtools/client/netmonitor/test/browser_net_cause_source_map.js` fails from the same reason? (i.e. different order of resources of various types due to batching)

Here is a list of tests that are failing on timeout since waiting for payloadReady that never happens.
Perhaps there could be common underlying issue

* devtools/client/netmonitor/test/browser_net_cause_source_map.js (passes with `devtools.target-switching.server.enabled=true`)
* devtools/client/netmonitor/test/browser_net_initiator.js (this report, passes with `devtools.target-switching.server.enabled=true`)
* devtools/client/netmonitor/test/browser_net_websocket_stacks.js
* devtools/client/netmonitor/test/browser_net_worker_stacks.js

Honza
Revision 4 by
on 
@bomsy: It is possible that `devtools/client/netmonitor/test/browser_net_cause_source_map.js` fails from the same reason? (i.e. different order of resources of various types due to batching)

Here is a list of tests that are failing on timeout since waiting for payloadReady that never happens.
Perhaps there could be common underlying issue

* devtools/client/netmonitor/test/browser_net_cause_source_map.js (passes with `devtools.target-switching.server.enabled=true` + patch from bug 1713607)
* devtools/client/netmonitor/test/browser_net_initiator.js (this report, passes with `devtools.target-switching.server.enabled=true`  + patch from bug 1713607)
* devtools/client/netmonitor/test/browser_net_websocket_stacks.js
* devtools/client/netmonitor/test/browser_net_worker_stacks.js

Honza

Back to Bug 1717050 Comment 1