Hmm On several PRs the

<http://docker_tests.rs|docker_tests.rs>

are failing with:

thread 'docker_tests::capture_exit_code_signal' panicked at 'called `Result::unwrap()` on an `Err` value: Unclassified("Failed to start Docker container `7108a6e8f2a9dff9fcf149008fba61b02a1e7209699279ac4d89fe3d1110fbe2` for image `busybox:1.34.1`: DockerResponseServerError { status_code: 500, message: \"exec: \\\"docker-init\\\": executable file not found in $PATH\" }")', process_execution/docker/src/docker_tests.rs:156:4

This is on the ARM boxes, maybe related to the re-kicking the machines yesterday?

is

docker

installed on them still?

Surely at some point it did, or else the test would've never passed?

I'm curious if the boxes got re-imaged somehow or were merely rebooted?

i’m going to take a look at this now.

The box wasn't re-imaged, just rebooted

it might have gotten package or OS upgrades. in any case!

Someone let me know when I can re-bump. These block 2.16

it should now be installed

sounds like you can

I read that as an instruction "we should now be installing it" instead of a report "it is now being installed"

but it is in past tense

Yeah I re-kicked the PyO3 bump

it should have been fixed this morning, yea. independently though, Github Actions has been super slow today… things have stayed queued for hours.

git clone

degradation totally brought work down yesterday

my job finally ran, and that shard looks fixed.

Time to start kicking jobs