Skip to content

rustpkg tests have too much output by default #7250

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

Closed
brson opened this issue Jun 20, 2013 · 1 comment
Closed

rustpkg tests have too much output by default #7250

brson opened this issue Jun 20, 2013 · 1 comment
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc

Comments

@brson
Copy link
Contributor

brson commented Jun 20, 2013

It is emitting lots of this:

time: 0.004 s   translation
time: 0.008 s   LLVM passes
warning: no debug symbols in executable (-arch x86_64)
time: 0.061 s   linking
note: build_crates: compiling src/bar-0.1/bench.rs
note: build_crates: destination dir is ./build/bar
time: 0.000 s   parsing
time: 0.007 s   expansion
time: 0.000 s   configuration
time: 0.000 s   maybe building test harness
time: 0.003 s   intrinsic injection
time: 0.000 s   extra injection
time: 0.000 s   ast indexing
time: 0.171 s   external crate/lib resolution
time: 0.000 s   language item collection
time: 0.181 s   resolution
time: 0.000 s   looking for entry point
time: 0.000 s   freevar finding
time: 0.000 s   region resolution
time: 0.000 s   region parameterization inference
time: 0.001 s   type collecting
time: 0.117 s   coherence checking
time: 0.001 s   type checking
time: 0.000 s   const marking
time: 0.000 s   const checking
time: 0.000 s   privacy checking
time: 0.000 s   effect checking
time: 0.000 s   loop checking
time: 0.000 s   compute moves
time: 0.000 s   match checking
time: 0.000 s   liveness checking
time: 0.000 s   borrow checking
time: 0.000 s   kind checking
time: 0.000 s   lint checking
time: 0.003 s   translation
time: 0.009 s   LLVM passes
warning: no debug symbols in executable (-arch x86_64)
time: 0.047 s   linking
time: 0.005 s   intrinsic injection
time: 0.000 s   extra injection
time: 0.000 s   ast indexing
time: 0.113 s   external crate/lib resolution
time: 0.000 s   language item collection
time: 0.113 s   resolution
time: 0.000 s   looking for entry point
time: 0.000 s   freevar finding
time: 0.000 s   region resolution
time: 0.000 s   region parameterization inference
time: 0.001 s   type collecting
time: 0.080 s   coherence checking
time: 0.000 s   type checking
time: 0.000 s   const marking
time: 0.000 s   const checking
time: 0.000 s   privacy checking
time: 0.000 s   effect checking
time: 0.000 s   loop checking
time: 0.000 s   compute moves
time: 0.000 s   match checking
time: 0.000 s   liveness checking
time: 0.000 s   borrow checking
time: 0.000 s   kind checking
time: 0.000 s   lint checking
time: 0.001 s   translation
time: 0.003 s   LLVM passes
warning: no debug symbols in executable (-arch x86_64)
time: 0.083 s   linking
note: build_crates: compiling src/foo-0.1/test.rs
note: build_crates: destination dir is ./build/foo
time: 0.000 s   parsing
time: 0.006 s   expansion
time: 0.000 s   configuration
time: 0.001 s   maybe building test harness
time: 0.002 s   intrinsic injection
time: 0.000 s   extra injection
time: 0.000 s   ast indexing
time: 0.127 s   external crate/lib resolution
time: 0.000 s   language item collection
time: 0.137 s   resolution
time: 0.000 s   looking for entry poin

It's hard to tell what the results are because there's a lot of information.

@ghost ghost assigned catamorphism Jun 20, 2013
@catamorphism
Copy link
Contributor

Yeah, I can take out the -Z time-passes (which I just added for debugging) pretty easily.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants