As a crate author, I'd like to be able to see if Crater is able to build my crate

[carols10cents]

This is a low-priority feature request at this time given other infrastructure needs, but I could see this increasing in priority someday as the ecosystem grows and reliance on Crater increases.

My understanding of the way Crater works is that for every experiment, Crater first tries to build+test all the crates it knows about with a "control" rustc. Then with a "candidate" rustc that contains some PR being evaluated, tries to build+test all the crates that were successfully built with the "control" rustc and reports the crates that fail with the "candidate" rustc. If this is not how Crater works, my request might not make sense ;)

There are ways that I can publish or neglect a crate that mean Crater is not ever able to build or test my crate with "control" rustc, so my crate is not helping Crater's evaluation.

As a crate author, I'd like to be able to see if my crate is being included or excluded in Crater experiments, and if it's being excluded, to see why so that I might fix it to have my crate included in Crater runs.

[Mark-Simulacrum]

In some sense, this will eventually be similar or the same as "does this crate have docs on docs.rs"? However, that won't give you tests pass/linking succeeds for the general case as we run the equivalent of cargo doc there.

(to be clear, the builder on docs.rs is currently different but we want to merge it with crater's)

[shepmaster]

I might be in the minority, but I’d also be interested in knowing if my crates ever fail any “candidate” run. I understand that this could have noise, but I think I’d be ok with that.

[jyn514]

(to be clear, the builder on docs.rs is currently different but we want to merge it with crater's)

The docs.rs builder now uses rustwide with some additional flags.