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

Switch to downloading dependencies from Github releases #3236

Merged
merged 1 commit into from
Nov 11, 2024

Conversation

Assumeru
Copy link
Contributor

@Assumeru Assumeru commented Nov 11, 2024

@psi29a psi29a merged commit 87c0972 into OpenMW:master Nov 11, 2024
@Assumeru
Copy link
Contributor Author

Uhh, this wasn't supposed to be merged.

I guess it's fine because the sync will override it?

@AnyOldName3
Copy link
Member

https://github.com/OpenMW/openmw/actions/runs/11778077287 says it didn't work anyway.

When I had to test the Actions after making a change, I made a branch on my fork and didn't need to make a PR for it to run. Except in the Actions tab, I can't see an attempted run for this branch in any of the normal places, so I guess that's just what it does when there's a syntax error.

@Assumeru
Copy link
Contributor Author

Yeah, I've got them running happily on my own branch now. I think the first one was weird because I didn't push the master branch first (so the Actions tab just said some stuff about adding them at all.)

https://github.com/Assumeru/openmw/actions/runs/11782120683

@AnyOldName3
Copy link
Member

That run's dying on https://gitlab.com/OpenMW/openmw/-/blob/master/components/config/launchersettings.cpp?ref_type=heads#L295, which I originally did with a default capture, and then had to stop because Clang -Werrored out because nothing was being captured as constexpr things don't need capturing. I'm guessing it's been broken since the relevant MR was merged.

@AnyOldName3
Copy link
Member

Yep https://github.com/OpenMW/openmw/actions/runs/11540499199/job/32121398575#step:12:711

It was failing before that pretty often due to the tests failing. That seemed to start with https://github.com/OpenMW/openmw/actions/runs/10697010351/job/29653330876#step:22:3202 a couple of months ago.

@Assumeru
Copy link
Contributor Author

@AnyOldName3
Copy link
Member

We've at least got stronger evidence that it was caused by https://gitlab.com/OpenMW/openmw/-/merge_requests/4336 (or at least one of the few immediately preceding it) as we've got the log of actions showing the crash wasn't happening, and the first failure was when that MR got merged. It was open for a week, and doesn't look like it was rebased, so with the rate things have been failing since its merge, we'd have expected at least one of the actions runs between it being branched and merged to have failed if it was a different MR that caused the problem.

@Assumeru
Copy link
Contributor Author

That does look pretty convincing. Hmm.

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.

3 participants