-
-
Notifications
You must be signed in to change notification settings - Fork 743
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
test runs hang frequently at the end #4350
Comments
After it hung, I hit Ctrl-C once:
|
note: pytest-timeout package can make it time out instead of hang. |
Note: In Travis CI my recent PR #4477 build on Python 3.6 had this issue too (only 3.6). |
@fantasya-pbem it happens very frequently, but root cause is unknown yet. |
I recently tried downgrading misc. packages (pytest, pluggy, pytest-xdist), but it didn't help. |
added
It seems to always (? or at least mostly) hang at Seen it for py35 and py36. |
Had a look at that test, looks mostly harmless. For now, I just merged #4481 into master and we'll see better where it is hanging. |
master branch at 6dd1491,
always hangs in |
let's see if it always hangs in test 2 now.
after splitting the hardlinks extraction test into 2, it became clear the issue only happens for partial extraction. |
it's a bug. the chunks needed for hardlink slaves are not preloaded (if the hardlink master is not also extracted), but the code later expects that they are, which makes it hang. some details while trying to fix this: most chunks preloaded in: code in expects preloaded chunks: |
…ckup#4350 also split the hardlink extraction test into 2 tests.
…ckup#4350 also split the hardlink extraction test into 2 tests. (cherry picked from commit f33f318)
slave hardlinks extraction issue, see #4350 (master)
slave hardlinks extraction issue, see #4350 (1.1-maint)
happens in 1.1-maint branch (e.g. 1.1.9), not sure about other branches.
tox runs on travis-ci and also in the vagrant machines frequently, but not always hang at the end (short before the test results are output). high cpu, no output.
could be related to coverage extension maybe?
also check if some version upgrade of testing tools / libs is causing this.
happens since ~4 weeks or so.
The text was updated successfully, but these errors were encountered: