Skip to content
Run experiments across parts of the Rust ecosystem!
Branch: master
Clone or download
bors Auto merge of #406 - pietroalbini:detect-yanked, r=pietroalbini
Detect crates with yanked dependencies and mark them as broken

This PR removes yet another source of errors.
Latest commit 76f728a Mar 12, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
assets results: rename build-fail:broken to broken:CATEGORY Mar 12, 2019
ci
docs
local-crates
src prepare: mark crates with yanked dependencies as broken Mar 12, 2019
templates results: add failure reason to build/test failures Nov 10, 2018
tests prepare: mark crates with yanked dependencies as broken Mar 12, 2019
.appveyor.yml
.gitattributes
.gitignore
.travis.yml
CONTRIBUTING.md Remove references to alternate way to run clippy Oct 8, 2018
Cargo.lock
Cargo.toml Use rust libraries instead of OpenSSL for HMAC Feb 18, 2019
README.md
blacklist.md
build.rs build.rs: keep track of git commit changes Sep 25, 2018
config.toml prepare: mark crates with yanked dependencies as broken Mar 12, 2019
find-bad-crates.py
rustfmt.toml
todo.md
tokens.example.toml tokens: correctly handle S3 tokens Jun 12, 2018

README.md

Crater Build Status

Crater is a tool to run experiments across parts of the Rust ecosystem. Its primary purpose is to detect regressions in the Rust compiler, and it does this by building large number of crates, running their test suites and comparing the results between two versions of the Rust compiler.

It can operate locally (with Docker as the only dependency) or distributed on the cloud. It only works on Linux at the moment, and it's licensed under both the MIT and Apache 2.0 licenses.

The current features of Crater are:

  • Discover Rust codebases on crates.io and GitHub
  • Execute experiments on custom Rust toolchains
  • Run cargo build and cargo test over all the discovered codebases
  • Build and test without dependency updates or network access
  • Run arbitrary tests over all the discovered codebases
  • Generate HTML reports with results and logs
  • Isolate tests in Docker containers

Crater is a successor to taskcluster-crater. It was subsequently named cargobomb before resuming the Crater name.

⚠️ DO NOT RUN CRATER IN AN UNSANDBOXED ENVIRONMENT ⚠️
Crater executes malicious code that will destroy what you love.

Documentation

Want to contribute to Crater? Check out the contribution guide.

User documentation:

Operations documentation:

Technical documentation:

You can’t perform that action at this time.