-
Notifications
You must be signed in to change notification settings - Fork 460
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
Regression on x86_64-apple-darwin between 1.0.93 and 1.0.100 #1170
Comments
The only change we introduce in 1.0.94 is for We changed It might be that the |
Not sure to start here, apologies. I'm not familiar with how @ijackson Does the problem go away on cc |
Hi. Thanks for looking. Maybe we can blunder through the forest together ? :-) I ran such a test in our CI (using the gitlab feature to set an env var). It doesn't seem to have made any significant difference, although the logs are gigantic and I'm not sure how I should interpret them. Test with cc 1.0.11 but not the extra env varhttps://gitlab.torproject.org/Diziet/arti/-/jobs/636719
Test with cc 1.0.11 and additional MACOSX_DEPLOYMENT_TARGET settinghttps://gitlab.torproject.org/Diziet/arti/-/jobs/637107
|
We have discovered that cached data ( |
It might be because we are missing some re-runs for files? |
Hi.
Since some time a little over a month ago, we have not been able to build with
--target x86_64-apple-darwin
. We see this:The breakage occurs when we try to
cargo update
. We know that 1.0.93 works, and that 1.0.100 doesn't.I'm afraid I haven't been able to narrow this down or bisect it properly, because it's in an environment I don't have local access to. The failure occurs for us in CI, with the image
amd64/rust:1.76.0-alpine3.18
.If it would be helpful, I could bisect it to a particular
cc
version.We do have some more information: logs from a failed build, and an MR in our tree proposing to pin
cc
, with some discussion.The text was updated successfully, but these errors were encountered: