Skip to content

Conversation

@nirbheek
Copy link
Member

Supposedly, breakage will happen in a few months.

@nirbheek nirbheek added the CI Continuous integration: Travis/Appveyor/Actions label Jul 26, 2024
@nirbheek nirbheek requested a review from jpakkane as a code owner July 26, 2024 01:03
@eli-schwartz
Copy link
Member

eli-schwartz@a73137d

At the time, I had discovered it kinda doesn't work, because updating to node 20 broke the os_comp tests. I never got around to redesigning them to free us of the oppression of github's action versions running inside arbitrary containers with older glibcs. And then just recently that hit us again. :)

@eli-schwartz
Copy link
Member

The CI results are in -- this breaks the workaround introduced in #13424.

@nirbheek
Copy link
Member Author

Hm, so we need to still use older node with the bionic job at least.

@nirbheek
Copy link
Member Author

Now the only things left to update are checkout (for bionic) and codecov (because there's a breaking change)

@nirbheek
Copy link
Member Author

No new build failures fwict, ok to merge @eli-schwartz?

@nirbheek
Copy link
Member Author

Will merge this in 24h if there are no objections. I have manually verified that the CI failures are not new.

@nirbheek nirbheek merged commit 2daf5f7 into mesonbuild:master Jul 30, 2024
@nirbheek nirbheek deleted the ci-warnings branch July 30, 2024 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Continuous integration: Travis/Appveyor/Actions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants