-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Clean up Solaris CI #126025
Comments
cc @psumbera Not to put you on the spot, but I was the only one at the time who knew to try to reach out to you when the build issue was in Solaris. Obviously, I don't think it was actually intrinsic to Solaris per se, mostly our naughty build script doing needless work, but you're probably more able to identify which parts of what we do are needless work. |
I would love to help here. But have no idea how it's supposed to work. Is there any documentation for it? |
nope lol |
There is documentation for the platform support and the target tier policy which Solaris has been effectively "grandfathered" in, allowing it to exist as tier 2 despite not having maintainers. There is documentation on how our Docker CI works in general. There is nothing documenting the Solaris toolchain script. |
I think I'm getting into it. I have Oracle Linux and I did:
And it seems to work as expected. I'm little bit confused with caching... But I have different question. I'm playing with it and I would like to build full Rust compiler for Solaris (not just std). But it fails. I tired NetBSD build and it fails the same way. So maybe I do something wrong.
Any idea about this? |
We should clean up our Solaris CI. The poorly-maintained build script recently caused a significant downtime, and even my fix was just a rude hack.
Alternately, we can decommission our Solaris CI!
If someone objects it would be great to have them formally write down their contact info in a platform support page for the targets.
The text was updated successfully, but these errors were encountered: