-
Notifications
You must be signed in to change notification settings - Fork 388
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
Fix build issues #206
Fix build issues #206
Conversation
I think the remaining issues can be fixed later (or the support for the affect targets be removed). Merging this PR will allows many of the queued PR to be tested and merged, so I think it is the away to go. |
Just as a heads up: currently there are 7 failing targets with this PR (after one small patch for xargo). Fortunately only two underlying issues are causing this:
Does somebody know how one could fix these? |
https://travis-ci.org/Bobo1239/cross/builds/432241101
@bgermann I believe this should've been fixed by rust-lang/cmake-rs#45 (also see Bobo1239@6b5266b) and iirc this error did disappear back then. Any clue why it's resurfacing now? |
alexcrichton/git2-rs@76f4b74 is the cause for the new failures. Fix: https://github.com/alexcrichton/git2-rs/pull/356 |
https://travis-ci.org/Bobo1239/cross/builds/433072223 Everything's green now 🍾 (even |
What needs to be done to get this merged? |
bors try (I can't remember if bors is setup for this project, will try a local build later on if not) |
Do note that two (or atleast the first) commits have to be added before everything's green: |
Ahh, thanks! Is there any reason not to apply those over this PR so everything is green? |
tryBuild failed |
@Bobo1239 possible but previous builds have worked fine. I think it is better to reduce the verbosity of the build first |
Build failed |
@Dylan-DPC Can you specify which previous builds you are referring to? It appears to me that previous builds were genuinely failing and before that (10 months ago) @japaric had the same issue. The last two green builds only became green after @ryankurte manually restarted the failing jobs. (Though the "bors try" run seems to have succeeded immediately.) Regardless of that, reducing the verbosity of the build should be as easy as removing this line in |
@Bobo1239 my bad. was probably thinking of some other repo. Yeah bors will fail even if we manually restart the builds on travis because it creates a new build. With regards to the travis thing, i think it is better to do it in a separate PR. will do that change right now. |
213: remove export to make CI process less verbose r=ryankurte a=Dylan-DPC The bors builds are failing probably because of the verbosity of the build. Removing this as per [this comment](#206 (comment)) Co-authored-by: Dylan DPC <[email protected]>
@Dylan-DPC and @ryankurte I've added the python workaround. Please consider this pragmatic solution so we can move this forward. |
@malbarbo thanks. The problem is we might not be able to merge it because it may still use the old configuration (at least on bors). |
Thanks for that @Dylan-DPC, I guess we'll need to remove it when #213 lands. bors retry |
206: Fix build issues r=Dylan-DPC a=malbarbo This fixes almost all current build issues. Only two issues are left: - thumb* tests, which requires using https://github.com/japaric/utest instead of https://github.com/japaric/cortest - netbsd build, which is failing with libc linking issues Co-authored-by: Marco A L Barbosa <[email protected]>
Seems to have worked :D Unfortunately this run has another spurious issue:
but I think this was just bad luck. Guess we'll need another run... |
Yeah it is just a network error |
Build failed |
@Dylan-DPC @ryankurte Can one of you start a (hopefully last) new run? |
bors retry |
bors: retry |
Seems that your message didn't reach bors? |
pong |
bors retry |
pong |
bors r+ p=10 |
206: Fix build issues r=jamesmunns a=malbarbo This fixes almost all current build issues. Only two issues are left: - thumb* tests, which requires using https://github.com/japaric/utest instead of https://github.com/japaric/cortest - netbsd build, which is failing with libc linking issues Co-authored-by: Marco A L Barbosa <[email protected]>
Build succeeded |
This fixes almost all current build issues. Only two issues are left: