-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
CI failure in rust / Windows #13236
Labels
Comments
gnomesysadmins
pushed a commit
to GNOME/librsvg
that referenced
this issue
May 27, 2024
Apparently, the latest stable 1.78.0 is causing linker errors when the librsvg DLL is being linked. Upstream Meson/Rust issue is outlined in [1]. Expect the Visual Studio CI job to pass, again :| ugh... :| [1]: mesonbuild/meson#13236
gnomesysadmins
pushed a commit
to GNOME/librsvg
that referenced
this issue
May 27, 2024
Apparently, the latest stable 1.78.0 is causing linker errors when the librsvg DLL is being linked. Upstream Meson/Rust issue is outlined in [1]. Expect the Visual Studio CI job to pass, again :| ugh... :| [1]: mesonbuild/meson#13236 Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/981>
eli-schwartz
added a commit
to eli-schwartz/meson
that referenced
this issue
Jun 4, 2024
It started failing CI as soon as the default shifted to 1.78. Something is broken and it prevents running stable CI. Tracking issue opened. We pin the version because that is the same way we handle CI for linux -- with the exception that Linux CI can upgrade itself as soon as we fix issues causing the CI Image Builder to jam itself, whereas unfortunately Windows will need to be manually unpinned, but such is life as a Windows supporter. Bug: mesonbuild#13236
soumyaDghosh
pushed a commit
to soumyaDghosh/meson
that referenced
this issue
Jun 4, 2024
It started failing CI as soon as the default shifted to 1.78. Something is broken and it prevents running stable CI. Tracking issue opened. We pin the version because that is the same way we handle CI for linux -- with the exception that Linux CI can upgrade itself as soon as we fix issues causing the CI Image Builder to jam itself, whereas unfortunately Windows will need to be manually unpinned, but such is life as a Windows supporter. Bug: mesonbuild#13236
jwieleRH
pushed a commit
to jwieleRH/meson
that referenced
this issue
Jun 5, 2024
It started failing CI as soon as the default shifted to 1.78. Something is broken and it prevents running stable CI. Tracking issue opened. We pin the version because that is the same way we handle CI for linux -- with the exception that Linux CI can upgrade itself as soon as we fix issues causing the CI Image Builder to jam itself, whereas unfortunately Windows will need to be manually unpinned, but such is life as a Windows supporter. Bug: mesonbuild#13236
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Possibly caused by a rust update?
Recent job manifesting the issue: https://dev.azure.com/jussi0947/jussi/_build/results?buildId=21182&view=logs&j=5015ea34-1c35-577b-b206-c8bea8465a58&t=00c5cf7c-b41c-5970-0bf5-8751e484378e&l=1920
The text was updated successfully, but these errors were encountered: