Skip to content
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

Fixes #27805 - adds missing snapshots for Bitrig and FreeBSD #27821

Merged
merged 1 commit into from
Aug 14, 2015
Merged

Fixes #27805 - adds missing snapshots for Bitrig and FreeBSD #27821

merged 1 commit into from
Aug 14, 2015

Conversation

@rust-highfive
Copy link
Collaborator

r? @alexcrichton

(rust_highfive has picked a reviewer for you, use r? to override)

@dhuseby
Copy link
Author

dhuseby commented Aug 13, 2015

doh!

@dhuseby dhuseby assigned alexcrichton and unassigned dhuseby Aug 13, 2015
@alexcrichton
Copy link
Member

@bors: r+ fe5336b

@dhuseby
Copy link
Author

dhuseby commented Aug 13, 2015

@alexcrichton I really need to figure out why the snapshots are building and being included automagically. Any ideas? Is it just test pass/compile failures or is it second-tier status?

@alexcrichton
Copy link
Member

We currently run make check on the snapshot bots, and I believe that because the auto bots are failing it means the snapshot bots will fail tests so the normal snapshot process doesn't work.

@dhuseby
Copy link
Author

dhuseby commented Aug 13, 2015

so the bitrig bot was working just fine until the new snapshots were made and added to src/snapshots.txt, then the compiles started failing because there wasn't a bitrig snapshot. AFAICT, the bitrig build bot should be able to produce snapshots. i'm less confident in the freebsd ones because there are some tests failing...at least on 32-bit for sure and maybe 64.

@alexcrichton
Copy link
Member

Yeah it looks like bitrig should have produced a snapshot, but here's the logs for why it failed: http://buildbot.rust-lang.org/builders/snap3-bitrig-64/builds/130/steps/compile/logs/stdio. Notably:

command timed out: 1800 seconds without output running ['gmake'], attempting to kill
process killed by signal 13
program finished with exit code -1

Perhaps it was swapping when compiling librustc? I've noticed it's lagged behind quite a bit on auto builds. If it was running both an auto build and a snap build it may have failed (we may just want to throttle the number of builds on the bot)

@dhuseby
Copy link
Author

dhuseby commented Aug 14, 2015

ah yeah, i was having some stability issues last week with the bitrig buildbot vm. it's been stable for the last week after upgrading the kernel and system libs.

@bors
Copy link
Contributor

bors commented Aug 14, 2015

⌛ Testing commit fe5336b with merge e907fab...

@bors bors merged commit fe5336b into rust-lang:master Aug 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants