Register snapshots (2015-05-24 ba0e1cd).

[eddyb]

No description provided.

[rust-highfive]

r? @alexcrichton

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

[alexcrichton]

Yay! Is this still blocked on anything @eddyb? I'd also like to get this in to get MSVC bootstrapping itself.

We've retroactively registered bitrig snapshots in the past, so we don't necessarily need to block on those becoming available.

[dhuseby]

My builder is back up and running now that I fixed the VM config. If we hold off for a few hours, we'll have a bitrig stage 3 snap to include.

[eddyb]

@dhardy the same build that failed twice, right? It would be nice for it to be the same revision.
@alexcrichton if you're okay with the zeroed hash and replacing it later (with a snapshot built from that same revision), feel free to r+.

[dhuseby]

@eddyb the snapshot at that revision is now building: http://buildbot.rust-lang.org/builders/snap3-bitrig-64/builds/124

[alexcrichton]

I'll throw this onto bors for now just to get it in the queue (may weed out some errors), and we can always pull in the bitrig snapshots once they're ready!

@bors: r+ 7eee86a

[eddyb]

@bors r=alexcrichton

[bors]

📌 Commit b368f7f has been approved by alexcrichton

[bors]

⌛️ Testing commit b368f7f with merge 7d71f50...

[bors]

💔 Test failed - auto-mac-64-opt

[eddyb]

@dhuseby Thanks for the fixing bitrig, seems we have a snapshot.

[eddyb]

@bors r=alexcrichton

[bors]

📌 Commit 377b090 has been approved by alexcrichton

[bors]

⌛️ Testing commit 377b090 with merge eb16ad6...

[bors]

☀️ Test successful - auto-linux-32-nopt-t, auto-linux-32-opt, auto-linux-64-nopt-t, auto-linux-64-opt, auto-linux-64-x-android-t, auto-mac-32-opt, auto-mac-64-nopt-t, auto-mac-64-opt, auto-win-gnu-32-nopt-t, auto-win-gnu-32-opt, auto-win-gnu-64-nopt-t, auto-win-gnu-64-opt

[alexcrichton]

I was a little surprised to see that usage of a const fn is stable today even if defining it is not. This means that calling UnsafeCell::new to create a static UnsafeCell is now stable (which I think was unintentional). I believe that @nikomatsakis is working on a patch to feature-gate usage, however.

[pythonesque]

Oh my god this is amazing.