-
Notifications
You must be signed in to change notification settings - Fork 683
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
Integrate the FreeBSD BuildBot #618
Conversation
bors.toml
Outdated
status = ["continuous-integration/travis-ci/push"] | ||
# Gate on Travis CI and Buildbot | ||
status = ["continuous-integration/travis-ci/push", | ||
"buildbot/nix-rust/nix fbsd11"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor nitpick, can you align the quotes? The off-by-two is bugging me.
This seems to only address x86_64 FreeBSD, do you have plans for i686? Or was #603 really just about x86_64? |
After my one comment is resolved, this LGTM. |
* Gate Bors on the FreeBSD 11 build * Remove the testless FreeBSD build from Travis * Promote x86_64-unknown-freebsd to Tier 1 Fixes nix-rust#603
@Susurrus it would be pretty easy to add an x86 worker. I'd like to do it, but I haven't gotten around to it yet. It would also be totally awesome to have an arm64 worker, which will be possible as soon as Scaleway.com's ARM64 VPSes go live. Right now they're just in preview mode. |
Let's do this. bors r+ |
Timed out |
Try again? BuildBot didn't build the merge commit (based on clicking the X and seeing fbsd11 not listed), but it built the newer commits done afterward (because fbsd11 is listed under the checkmark). |
I noticed that. I changed one thing in BuildBot's configuration, but I didn't expect it to solve this particular problem. I guess we may as well try, try again. The worst case is that BuildBot is intermittent. If that happens, we'll have to degate Bors on it. |
Build succeeded |
Fixes #603