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

update registry on every build #2643

Closed
dhardy opened this issue May 4, 2016 · 3 comments
Closed

update registry on every build #2643

dhardy opened this issue May 4, 2016 · 3 comments

Comments

@dhardy
Copy link

dhardy commented May 4, 2016

Looks like #991 again. This is happening on one project but not another. The below is after git stash; I get the same with non-compiling code.

dhardy@localhost:~/other/pippin$ cargo build -v
    Updating registry `https://github.com/rust-lang/crates.io-index`
       Fresh winapi v0.2.6
       Fresh libc v0.2.10
       Fresh winapi-build v0.1.1
       Fresh gcc v0.3.27
       Fresh rustc-serialize v0.3.19
       Fresh log v0.3.6
       Fresh regex-syntax v0.2.2 (file:///home/dhardy/other/regex)
       Fresh vec_map v0.6.0
       Fresh byteorder v0.5.1
       Fresh rand v0.3.14
       Fresh libc v0.1.12
       Fresh num-traits v0.1.32
       Fresh hashindexed v0.1.0
       Fresh memchr v0.1.11
       Fresh num-integer v0.1.32
       Fresh aho-corasick v0.4.1
       Fresh kernel32-sys v0.2.2
       Fresh num-iter v0.1.32
       Fresh regex v0.1.48 (file:///home/dhardy/other/regex)
       Fresh walkdir v0.1.5
       Fresh time v0.1.35
       Fresh num v0.1.32
       Fresh rust-crypto v0.2.35
       Fresh chrono v0.2.21
   Compiling pippin v0.0.0 (file:///home/dhardy/other/pippin)
     Running `rustc src/lib.rs --crate-name pippin --crate-type lib -g --out-dir /home/dhardy/other/pippin/target/debug --emit=dep-info,link -L dependency=/home/dhardy/other/pippin/target/debug -L dependency=/home/dhardy/other/pippin/target/debug/deps --extern crypto=/home/dhardy/other/pippin/target/debug/deps/libcrypto-bae5fed23a1cbaaf.rlib --extern vec_map=/home/dhardy/other/pippin/target/debug/deps/libvec_map-052ff1ed2f091ceb.rlib --extern log=/home/dhardy/other/pippin/target/debug/deps/liblog-342ffb7444a9471d.rlib --extern regex=/home/dhardy/other/pippin/target/debug/deps/libregex-9852f3132a559d8d.rlib --extern walkdir=/home/dhardy/other/pippin/target/debug/deps/libwalkdir-e99b970d5c826b1c.rlib --extern rand=/home/dhardy/other/pippin/target/debug/deps/librand-c724acb3942597d1.rlib --extern chrono=/home/dhardy/other/pippin/target/debug/deps/libchrono-b7e7e442a0c8b7fb.rlib --extern hashindexed=/home/dhardy/other/pippin/target/debug/deps/libhashindexed-cb1e5df0bbfe4587.rlib --extern byteorder=/home/dhardy/other/pippin/target/debug/deps/libbyteorder-8ad3fd7ac7478b9a.rlib -L native=/home/dhardy/other/pippin/target/debug/build/rust-crypto-ee392cda555c7573/out`
dhardy@localhost:~/other/pippin$ cargo build -v
    Updating registry `https://github.com/rust-lang/crates.io-index`
       Fresh libc v0.1.12
       Fresh regex-syntax v0.2.2 (file:///home/dhardy/other/regex)
       Fresh vec_map v0.6.0
       Fresh winapi v0.2.6
       Fresh winapi-build v0.1.1
       Fresh num-traits v0.1.32
       Fresh rustc-serialize v0.3.19
       Fresh log v0.3.6
       Fresh libc v0.2.10
       Fresh gcc v0.3.27
       Fresh byteorder v0.5.1
       Fresh hashindexed v0.1.0
       Fresh num-integer v0.1.32
       Fresh memchr v0.1.11
       Fresh rand v0.3.14
       Fresh num-iter v0.1.32
       Fresh aho-corasick v0.4.1
       Fresh kernel32-sys v0.2.2
       Fresh num v0.1.32
       Fresh regex v0.1.48 (file:///home/dhardy/other/regex)
       Fresh walkdir v0.1.5
       Fresh time v0.1.35
       Fresh rust-crypto v0.2.35
       Fresh chrono v0.2.21
       Fresh pippin v0.0.0 (file:///home/dhardy/other/pippin)
dhardy@localhost:~/other/pippin$ cargo build 
    Updating registry `https://github.com/rust-lang/crates.io-index`

dhardy@localhost:~/other/pippin$ cargo --version && rustc --version
cargo 0.10.0-nightly (4576ae2 2016-03-16)
rustc 1.9.0-nightly (6e0f2f2f0 2016-03-16)

Same after updating rust to the latest nightly:

dhardy@localhost:~/other/pippin$ g stash
Saved working directory and index state WIP on master: 3fc332e Compile fixes for new VecMap version
HEAD is now at 3fc332e Compile fixes for new VecMap version
dhardy@localhost:~/other/pippin$ cargo build
    Updating registry `https://github.com/rust-lang/crates.io-index`
   Compiling pippin v0.0.0 (file:///home/dhardy/other/pippin)
dhardy@localhost:~/other/pippin$ cargo build -v
    Updating registry `https://github.com/rust-lang/crates.io-index`
       Fresh vec_map v0.6.0
       Fresh num-traits v0.1.32
       Fresh byteorder v0.5.1
       Fresh hashindexed v0.1.0
       Fresh winapi v0.2.6
       Fresh gcc v0.3.27
       Fresh libc v0.1.12
       Fresh rustc-serialize v0.3.19
       Fresh regex-syntax v0.2.2 (file:///home/dhardy/other/regex)
       Fresh libc v0.2.10
       Fresh num-integer v0.1.32
       Fresh log v0.3.6
       Fresh winapi-build v0.1.1
       Fresh rand v0.3.14
       Fresh memchr v0.1.11
       Fresh num-iter v0.1.32
       Fresh aho-corasick v0.4.1
       Fresh num v0.1.32
       Fresh regex v0.1.48 (file:///home/dhardy/other/regex)
       Fresh kernel32-sys v0.2.2
       Fresh walkdir v0.1.5
       Fresh time v0.1.35
       Fresh rust-crypto v0.2.35
       Fresh chrono v0.2.21
       Fresh pippin v0.0.0 (file:///home/dhardy/other/pippin)
dhardy@localhost:~/other/pippin$ cargo --version && rustc --version
cargo 0.11.0-nightly (afac7fc 2016-04-27)
rustc 1.10.0-nightly (8da2bcac5 2016-04-28)
@alexcrichton
Copy link
Member

Do you perhaps have path overrides locally? Those have been known to cause these sorts of spurious updates

@dhardy
Copy link
Author

dhardy commented May 4, 2016

Yes I did, that helps me. But sounds like there's still an unfixed issue? I'll let you close/repurpose this one. Thanks!

BTW the path override was defined for both projects I tested but did not apply to the one which did not update the registry on every build.

@alexcrichton
Copy link
Member

Oh good! Or at least it wasn't a new bug...

In any case, that's tracked here: #2041, so closing in favor of that

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

No branches or pull requests

2 participants