-
Notifications
You must be signed in to change notification settings - Fork 51
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
modules/kvs: Cleanup content_load_completion() #1079
Conversation
Remove unnecessary cache_entry_create() call, as it is impossible to reach.
Hmmm, on one travis build
both tests pass, but get an error, presumably when t1006 is torn down. Wonder if there is a corner case I'm not seeing that this code cleanup is bad. |
Hmm, sort of perplexed by this. Both tests in t1006-apidisconnect.t pass. So the error appears to come outside of those tests. Presumably on teardown of the tests. But there's nothing in sharness or tap that appears to kill anything (such as if its hung). So I have no idea where the signal 9 (SIGKILL) came from. |
|
@garlick Ahh, I didn't think of the kill coming from within flux. The question is if this was a racy/bug hang or unlucky/slow scheduling. I'm thinking the latter, as if my patch was a real bug it would have asserted with SIGABRT and that would have been returned instead SIGKILL. Lets see if travis hits it regularly. Restarting. |
api-disconnect didn't appear this time. But did hit #1063.
Lets give travis another shot at a perfect run. |
Codecov Report
@@ Coverage Diff @@
## master #1079 +/- ##
==========================================
+ Coverage 77.92% 78.03% +0.11%
==========================================
Files 150 150
Lines 25965 25963 -2
==========================================
+ Hits 20233 20261 +28
+ Misses 5732 5702 -30
|
This seems good, and hard to imagine how it could be linked to the spurious travis problems. Merging. |
Remove unnecessary cache_entry_create() call, as it is impossible
to reach.