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

The first two tests are blocking for over 60 seconds in Travis #41

Open
mssun opened this issue Aug 2, 2018 · 4 comments
Open

The first two tests are blocking for over 60 seconds in Travis #41

mssun opened this issue Aug 2, 2018 · 4 comments
Labels
help wanted Extra attention is needed
Projects

Comments

@mssun
Copy link
Contributor

mssun commented Aug 2, 2018

I don't know why the first tests are always blocking for over 60 seconds. However, after the blocking issue, all testcases can be run without any problem.

test gnu::arch::test_x86_64 ... test gnu::arch::test_x86_64 has been running for over 60 seconds
test gnu::base32::test_decode ... test gnu::base32::test_decode has been running for over 60 seconds
@Arcterus
Copy link
Contributor

Arcterus commented Aug 2, 2018

We might want to open this as an issue in assert_cmd. It's hard to replicate though as it only seems to occur on Travis.

@Arcterus
Copy link
Contributor

Arcterus commented Aug 2, 2018

Haven't really checked to see what is different between the targets but the COVERAGE=1 target never has this issue (at least for the 5 or so builds I've checked).

@mssun
Copy link
Contributor Author

mssun commented Aug 2, 2018

Oh, that's probably because the COVERAGE=1 target does not run tests in parallel.

I think @epage has understood our issue and started working on it.

@Arcterus
Copy link
Contributor

Arcterus commented Aug 2, 2018

Ah, that makes sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
Testing
  
TODO
Development

No branches or pull requests

2 participants