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
rofi: 1.4.2 -> 1.5.0 #34519
rofi: 1.4.2 -> 1.5.0 #34519
Conversation
btw: Building fails because one test fails. |
@GrahamcOfBorg build rofi |
Failure on x86_64-darwin (full log) Partial log (click to expand)
|
Failure on x86_64-linux (full log) Partial log (click to expand)
|
Failure on aarch64-linux (full log) Partial log (click to expand)
|
nitpick: The URL is outdated. If you visit the homepage noted in the meta attributes then you will be greeted with a deprecation warning and shortly after that redirected to the GitHub repository. So far I suspect the reason the (gtk settings) test is failing to be because our sandboxed builders do not have a proper $HOME? I'll try to investigate further soon. |
changelog for the curious https://github.com/DaveDavenport/rofi/blob/next/Changelog |
@GrahamcOfBorg build rofi |
Failure on x86_64-linux (full log) Partial log (click to expand)
|
Failure on aarch64-linux (full log) Partial log (click to expand)
|
Failure on x86_64-darwin (full log) Partial log (click to expand)
|
e53ced3
to
da9a68f
Compare
@GrahamcOfBorg build rofi |
1 similar comment
@GrahamcOfBorg build rofi |
Failure on x86_64-darwin (full log) Partial log (click to expand)
|
Failure on x86_64-linux (full log) Partial log (click to expand)
|
I don't even understand what the error is... and why does github say "All checks have passed" despite the bot failing? |
The @GrahamcOfBorg builds are not part of the normal github checks. The Mac build most likely fails because some Mac specific library isn't being linked.. I doubt the previous versions did build there. |
Failure on aarch64-linux (full log) Partial log (click to expand)
|
According to the logs on |
Yes ,that is the "subprojects/libnkutils/tests/gtk-settings.test" which was introcuded with this bump IIRC. It probably assumes the ability to write to $HOME which might not be writable during test execution/at all? |
Well, |
Maybe the test requires X? I guess we generally just disable such tests, although in principle |
Maybe try this? |
da9a68f
to
7e5fd98
Compare
With the change suggested by @Mic92 this fails still:
Homepage updated, though. |
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)Does not build on my machine... though I have no time to investigate right now.
Feel free to reuse this patch.