- Ya
- 25 Agosti 2026, 14:35 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 66bab9e
The build has failed on every push since 2026-08-15 and it is not the code. The log shows npm ci dying with ERR_SSL_CIPHER_OPERATION_FAILED and ossl_gcm_stream_update — an AES-GCM tag mismatch, i.e. TLS detecting that the payload was corrupted in transit. The same docker build run by hand on the same runner completes all 34 steps. This image pulls the whole Meet dependency tree, by far the largest transfer any build on this runner makes, which is why it is the one that keeps losing the dice roll. It is the same corruption class documented for this machine in August, on a link that was supposedly replaced — worth knowing it is back. TLS aborts on a corrupt record rather than caching it, so a retry lands on a clean transfer. That is exactly the remedy the Maven builds already carry, and the reason they kept passing while this one did not. node_modules is cleared between attempts so a half-written tree cannot be mistaken for a good one, and the step fails loudly if all three attempts fail. Applied to the sidecar stage too, for the same reason.