logging: Redirect yamux warnings/errors to logger#89
logging: Redirect yamux warnings/errors to logger#89sboeuf merged 1 commit intokata-containers:masterfrom
Conversation
|
/cc @grahamwhaley. |
|
Build failed (third-party-check pipeline) integration testing with
|
|
Nice fix (I'd not twigged we could link the yamux with a writer to the log), but CI is not happy: |
|
ugh - that's going to be fun to debug ;) |
466d8c2 to
6cbfedd
Compare
|
Fixed it! @bergwolf - ptal. |
|
Build failed (third-party-check pipeline) integration testing with
|
6cbfedd to
921f4f2
Compare
Codecov Report
@@ Coverage Diff @@
## master #89 +/- ##
==========================================
- Coverage 37.74% 37.26% -0.49%
==========================================
Files 2 2
Lines 257 263 +6
==========================================
+ Hits 97 98 +1
- Misses 149 154 +5
Partials 11 11 |
|
That's distressing - |
|
Build failed (third-party-check pipeline) integration testing with
|
921f4f2 to
db780f4
Compare
|
Effectively blocked on #90 (as that contains a fix for the Travis OSX bash failure). |
|
Build failed (third-party-check pipeline) integration testing with
|
|
@jodh-intel #90 has been merged, please rebase this one ! |
db780f4 to
b476458
Compare
|
Hi @sboeuf - branch updated. |
|
Build failed (third-party-check pipeline) integration testing with
|
|
/retest <--i wish this worked? |
|
@egernst - you wish we had a 'trigger phrase' for Jenkins we could use in comments.... well, that is a feature supported in the github plugins we use in Jenkins afaik - we would just have to define it, configure it, and turn it on... |
|
Well, there does appear to be a test race here. I can force it on go 1.8 and 1.10 but it's easier to see on go 1.8. I'm still digging as the main code fires off go routines... that fire off go routines (in multiple parts of the code). And those go routines are unstoppable fwics as they are doing I/O copy. I'll take another look tomorrow but might need to get @sboeuf / @bergwolf to take a look, being the original authors of the go routine code. |
b476458 to
54eab20
Compare
|
Build failed (third-party-check pipeline) integration testing with
|
|
@jodh-intel Could you give a pointer to the logs of the race somewhere? |
54eab20 to
0569fc2
Compare
|
Hi @bergwolf - yep, if you look at the travis log... |
|
Build failed (third-party-check pipeline) integration testing with
|
|
@jodh-intel I think the problem is that the yamux session is not closed properly. Please see if #94 fixes the race. |
|
Blocked on #94 (I also need to remove the first commit). |
|
@jodh-intel please rebase now that #94 has been merged :) |
Capture yamux messages to the logger. Fixes kata-containers#88. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
0569fc2 to
ec252d8
Compare
|
Reworked now that #94 has landed. Ping @kata-containers/proxy. |
|
OK, I think we are in the same 'the CIs that failed do not matter' situation here:
None of the failing CIs is 'required', so I can press the big |
|
Build failed (third-party-check pipeline) integration testing with
|
|
@grahamwhaley yes I agree this can be merged. |
Capture yamux messages to the logger.
Fixes #88.
Signed-off-by: James O. D. Hunt james.o.hunt@intel.com