Skip to content
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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

gitforwindowshelper[bot]
Copy link

Signed-off-by: Matthias Aßhauer <mha1993@live.de>
@rimrul rimrul marked this pull request as ready for review June 29, 2024 16:08
@rimrul
Copy link
Member

rimrul commented Jun 29, 2024

/deploy

The workflow run was started.

@dscho
Copy link
Member

dscho commented Jul 1, 2024

@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?

@rimrul
Copy link
Member

rimrul commented Jul 2, 2024

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 build mingw-w64-llvm step and all later steps where showing the little canceled octagons with the exclamation mark.

@dscho
Copy link
Member

dscho commented Jul 2, 2024

The run was in a weird semi-running state when I canceled it. The job was showing as running at the top, but the build mingw-w64-llvm step and all later steps where showing the little canceled octagons with the exclamation mark.

Probably yet another GitHub incident...

@dscho
Copy link
Member

dscho commented Jul 2, 2024

Let's just try this again.

@rimrul
Copy link
Member

rimrul commented Jul 2, 2024

Also note that attempt 1 got stuck at

[4989/5000] Linking CXX static library lib\libclangTidyHICPPModule.a

and attempt 2 at

[4987/5000] Linking CXX executable bin\obj2yaml.exe

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?

@dscho
Copy link
Member

dscho commented Jul 2, 2024

That seems oddly close to each other

Indeed... We'll see. Maybe it gets miraculously "unstuck". 🤞

@dscho
Copy link
Member

dscho commented Jul 2, 2024

We should probably start paying attention in 4h from now.

@rimrul
Copy link
Member

rimrul commented Jul 2, 2024

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 build mingw-w64-llvm step and all later steps where showing the little canceled octagons with the exclamation mark.

@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.

@dscho
Copy link
Member

dscho commented Jul 2, 2024

I have canceled it. Strange. Are we running into a self-imposed timeout that is somehow not heeded by the runner?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[New mingw-w64-llvm version] llvm: update to 18.1.8
2 participants