-
Notifications
You must be signed in to change notification settings - Fork 64
Snapshot build (2022.01.15 ~ 2022.01.17) failed #267
Comments
What is interesting is that the first failure log is Due to #264 ? |
The error in
|
I successfully executed the failure command after loading the failure image.
So this is not a reproducible issue. |
We automatically retry on failure; the failure log shows an attempt failed, but we then tried again on another machine and it worked It's worth checking the dmesg logs etc to see if there's anything correlating to the non-reproducible error (it does happen occassionally, especially on 11, but without a reliable repro) But a single attempt failing isn't necessarily an issue worth investigating |
I killed the hanging EC2 instance and terminated all running step functions. However, the 2022.01.18 build still failed due to gcc crashing.
|
let's kick off another build just for 11, in case it's intermittent (to hopefully unblock this weeks' release), but also try and pull up the logs for what happened there. >2h is ok, > 3h is not. |
Sorry, it's not a timeout. It's due to gcc crash. |
Why didn't the step function retry? |
Is it possible that the step function did retry, but GCC crashed every time? A GCC crash is not neccessarily a GCC bug - e.g. it could be the kernel killing it due to running out of memory. Needs correlating with syslog/dmesg |
I think so. The previous failure log file |
I triggered |
Now triggering |
No description provided.
The text was updated successfully, but these errors were encountered: