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.

Sign up for GitHub

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

Jump to bottom

Extract resolver tests to their own crate #7011

Merged
merged 2 commits into from
Jun 18, 2019
Merged

Extract resolver tests to their own crate #7011

merged 2 commits into from
Jun 18, 2019

Commits on Jun 18, 2019

  1. Move the crates-io crate to a crates directory 

    That way when we add more crates we've got a place to put them!
    @alexcrichton
    alexcrichton committed Jun 18, 2019
    Configuration menu
    Copy the full SHA
    e449cb2 View commit details
    Browse the repository at this point in the history

  2. Extract resolver tests to their own crate 

    These tests take a good amount of time to run locally and they're also
causing a lot of dependencies to get pulled into rust-lang/rust, so
let's have a separate crate that we just test on our own CI
    @alexcrichton
    alexcrichton committed Jun 18, 2019
    Configuration menu
    Copy the full SHA
    290a727 View commit details
    Browse the repository at this point in the history