-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mingw-w64-llvm: update to 18.1.8 #124
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Matthias Aßhauer <mha1993@live.de>
/deploy The workflow run was started. |
@rimrul I see that there was a long gap between the last log message and the time you canceled the run. Any clue what was going on there? |
I'm not sure what happened. The run was in a weird semi-running state when I canceled it. The job was showing as running at the top, but the |
Probably yet another GitHub incident... |
Let's just try this again. |
Also note that attempt 1 got stuck at
and attempt 2 at
That seems oddly close to each other, even if it's not the same spot (and the order of entries isn't deterministic). Maybe the issue happens at a certain time into the build? |
Indeed... We'll see. Maybe it gets miraculously "unstuck". 🤞 |
We should probably start paying attention in 4h from now. |
@dscho it's doing it again. The time is still ticking up on the current step, but they have the canceled icon again and the current step doesn't expand. |
I have canceled it. Strange. Are we running into a self-imposed timeout that is somehow not heeded by the runner? |
This closes git-for-windows/git#5029