-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
sharness test failure #1243
Comments
Yeah i sometimes see this-- any ideas? fuse stuck? |
Yeah I also sometimes see this. |
I havent seen this for a while, but its likely thats because we don't run fuse tests hardly ever. I'll leave this open for now. |
We should be running those always. Travis CI has supported fuse for a long Cc @chriscool thoughts?
|
Yeah, we should have been doing that and we probably should have merged at least some parts of this PR that fixed fuse problems: |
This problem still exists. FUSE related tests are not automated. They do not seem to be run by anyone manually either. When I run the sharness locally on Linux, the actual issue seems to be that Possible options I see:
|
FUSE currently is in very bad state it has bigger problems than sharness not running, for example our unit tests for FUSE are hanging in the kernel. After 0.4.5 is released we will try updating the fuse lib to check if it fixes any problems, see: #3414 and we can proceed from there. |
We've updated our fuse libs. Can someone re-verify that this is an issue? |
Ran this in a loop for 10+ mins without a single fail, I'll call this fixed. |
set my desktop to continually run tests on master over and over again, came back to find it had failed here.
The text was updated successfully, but these errors were encountered: