Investigate CircleCI errors: "Too long with no output (exceeded 10m0s)"

[alisterscott]

We started seeing these around the same time we moved to using the CircleCI prebuilt docker browser containers (over our own docker container)

Example build: https://circleci.com/gh/Automattic/wp-e2e-tests/17949

#!/bin/bash -eo pipefail
./scripts/run-wrapper.sh

> wp-e2e-tests@0.0.1 test /home/circleci/wp-e2e-tests
> ./run.sh ${TESTARGS:-$npm_package_defaultTestArgs}

Parallel execution details:
mobile=0, desktop=1, node=0, total=2
Executing tests at mobile screen width
Magellan 8.8.6
Will try to load configuration from default of ./magellan.json
Loaded configuration from:  /home/circleci/wp-e2e-tests/magellan.json
Magellan is creating temporary files at: /home/circleci/wp-e2e-tests/temp
Sauce configuration OK
The $NODE_CONFIG environment variable is malformed JSON
[INFO] [Mocha Plugin] Scanning test files for tests ...
[INFO] [Mocha Plugin] Found 38 tests in test files

Running 38 tests with 3 workers with chrome

--> Worker 3, mock port:12006, running test: [WPCOM] View site from sidebar: (mobile) @parallel @jetpack @visdiff @chrome 
--> Worker 2, mock port:12003, running test: [WPCOM] Plans: (mobile) @parallel @jetpack @chrome 
--> Worker 1, mock port:12000, running test: [WPCOM] Managing Domains: (mobile) @parallel @chrome 
(1 / 38) <-- Worker 2 PASS  [WPCOM] Plans: (mobile) @parallel @jetpack @chrome  
--> Worker 2, mock port:12009, running test: [WPCOM] Managing Domain Mapping: (mobile) @parallel @chrome 
(2 / 38) <-- Worker 1 FAIL (will retry).  Spent 72765 msec [WPCOM] Managing Domains: (mobile) @parallel @chrome  
--> Worker 1, mock port:12012, running test: [WPCOM] Editor: Media Upload (mobile) @parallel @jetpack @chrome 
(3 / 38) <-- Worker 2 PASS  [WPCOM] Managing Domain Mapping: (mobile) @parallel @chrome  
--> Worker 2, mock port:12015, running test: [WPCOM] Editor: Posts (mobile) Public Posts: @parallel @jetpack @chrome 
(4 / 38) <-- Worker 1 PASS  [WPCOM] Editor: Media Upload (mobile) @parallel @jetpack @chrome  
--> Worker 1, mock port:12018, running test: [WPCOM] Editor: Posts (mobile) Basic Public Post @canary @parallel @jetpack @chrome 
(5 / 38) <-- Worker 2 PASS  [WPCOM] Editor: Posts (mobile) Public Posts: @parallel @jetpack @chrome  
--> Worker 2, mock port:12021, running test: [WPCOM] Editor: Posts (mobile) Schedule Basic Public Post @parallel @jetpack @chrome 
(6 / 38) <-- Worker 1 PASS  [WPCOM] Editor: Posts (mobile) Basic Public Post @canary @parallel @jetpack @chrome  
--> Worker 1, mock port:12024, running test: [WPCOM] Editor: Posts (mobile) Private Posts: @parallel @jetpack @chrome 
Too long with no output (exceeded 10m0s)

[alisterscott]

Maybe the no-sandbox flag? Will try a PR without this set: https://discuss.circleci.com/t/running-browser-tests/10998/9

[alisterscott]

Haven't seen this one happening in some time - closing (for now)