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

vec_deque::tests::test_drain panicking on debug build #29492

Closed
pnkfelix opened this issue Oct 31, 2015 · 10 comments
Closed

vec_deque::tests::test_drain panicking on debug build #29492

pnkfelix opened this issue Oct 31, 2015 · 10 comments

Comments

@pnkfelix
Copy link
Member

vec_deque::tests::test_drain panicking on debug build

Here are my configure switches:

CFG_CONFIGURE_ARGS   := --enable-debug --enable-optimize --enable-ccache --prefix=~/opt/rust-dbg --disable-optimize-tests --disable-llvm-assertions

I suspect the important bit there is the --enable-debug.

When I run make check, it fails during collectionstest:

failures:                                                                                                         

---- vec_deque::tests::test_drain stdout ----                                                                     
        thread 'vec_deque::tests::test_drain' panicked at 'dst=0 src=7 len=2 cap=8', /home/fklock/Dev/Mozilla/rust.git/src/libcollections/vec_deque.rs:178                                                                         


failures:
    vec_deque::tests::test_drain

test result: FAILED. 18 passed; 1 failed; 0 ignored; 0 measured

I'm not familiar with the code in question, so its not immediately apparent if this is just a case of an invalid assertion, or some deeper violation of a structural invariant.

@Gankra
Copy link
Contributor

Gankra commented Oct 31, 2015

cc @mystor

@mystor
Copy link
Contributor

mystor commented Oct 31, 2015

I'll try to look at this tonight. Not sure why that would be happening :-/

bors added a commit that referenced this issue Nov 3, 2015
I think this should fix the test failures in debug mode from #29492

The assertion was written incorrectly, and I don't like the way the new assertion is written, but I _think_ it does the right thing now.
@apasel422
Copy link
Contributor

Was this fixed by #29545?

@mystor
Copy link
Contributor

mystor commented Nov 4, 2015

yes, I believe it was.

@bluss
Copy link
Member

bluss commented Nov 4, 2015

How can it have escaped the buildbots in the first place?

@mystor
Copy link
Contributor

mystor commented Nov 4, 2015

@bluss I guess tests are not run in debug mode, so debug assertions aren't hit? Who knows.

@bluss
Copy link
Member

bluss commented Nov 4, 2015

That sounds terrifying

@apasel422
Copy link
Contributor

@bluss The debug buildbot doesn't run tests. CC #27010.

@alexcrichton
Copy link
Member

Yeah currently the builder that builds the standard library in debug mode is too slow to also run tests unfortunately :(

@Gankra
Copy link
Contributor

Gankra commented Nov 4, 2015

One of many reasons why debug asserts are unfortunately borderline useless in std. :(

At least it was the test that was broken, and not the code!

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

6 participants