ruff icon indicating copy to clipboard operation
ruff copied to clipboard

`wasm-pack` test is unreliable

Open charliermarsh opened this issue 2 years ago • 6 comments
trafficstars

See: https://github.com/charliermarsh/ruff/actions/runs/3794761527/jobs/6453331265.

charliermarsh avatar Dec 28 '22 15:12 charliermarsh

What I don't understand - and I noticed that in multiple runs - is why the operation is being canceled. Many times the tests succeeded.

running 3 tests

test ruff::lib_wasm::test::empty_config ... ok
test ruff::lib_wasm::test::partial_config ... ok
test ruff::lib_wasm::test::partial_nested_config ... ok

test result: ok. 3 passed; 0 failed; 0 ignored

Error: The operation was canceled.

squiddy avatar Dec 28 '22 15:12 squiddy

Yeah, trying to find any relevant issues etc. but not seeing anything.

charliermarsh avatar Dec 28 '22 15:12 charliermarsh

I don't know if this is just a symptom of a different failure, but when it fails in this way, we never see the other test suites skip execution:

Screen Shot 2022-12-28 at 10 24 08 AM Screen Shot 2022-12-28 at 10 24 12 AM

charliermarsh avatar Dec 28 '22 15:12 charliermarsh

I'll try setting --lib for now... I dunno.

charliermarsh avatar Dec 28 '22 15:12 charliermarsh

I'm also seeing this.. which isn't that helpful. I was thinking that maybe it's just being canceled because a new workflow was scheduled, but that doesn't seem to be the case. I would also kinda rule out memory issues, we're not even running headless browsers for testing..

2022-12-28T15:22:07.1731677Z running 3 tests
2022-12-28T15:22:07.1831067Z 
2022-12-28T15:22:07.2165473Z test ruff::lib_wasm::test::empty_config ... ok
2022-12-28T15:22:07.2217990Z test ruff::lib_wasm::test::partial_config ... ok
2022-12-28T15:22:07.2433964Z test ruff::lib_wasm::test::partial_nested_config ... ok
2022-12-28T15:22:07.2457576Z 
2022-12-28T15:22:07.2459785Z test result: ok. 3 passed; 0 failed; 0 ignored
2022-12-28T15:22:07.2460027Z 
2022-12-28T15:22:41.4902290Z ##[error]Process completed with exit code 143.
2022-12-28T15:22:41.4984194Z ##[error]The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

squiddy avatar Dec 28 '22 15:12 squiddy

Well, actually.. when you start searching for the "shutdown signal" thing, numerous issues popup about people's jobs being canceled. Most often due to resource limits.

For example: https://github.com/actions/runner-images/issues/6680 One response: https://github.com/actions/runner-images/issues/6680#issuecomment-1335778010

squiddy avatar Dec 28 '22 15:12 squiddy

I don't remember having seen this in months.

MichaReiser avatar Feb 23 '24 22:02 MichaReiser