Ignore fifo error when using v2 multi-container shim#3536
Conversation
|
Build succeeded.
|
Codecov Report
@@ Coverage Diff @@
## master #3536 +/- ##
==========================================
- Coverage 44.94% 42.21% -2.73%
==========================================
Files 115 124 +9
Lines 12790 13692 +902
==========================================
+ Hits 5748 5780 +32
- Misses 6170 7039 +869
- Partials 872 873 +1
Continue to review full report at Codecov.
|
|
LGTM |
bc690df to
751c1b6
Compare
|
Build succeeded.
|
751c1b6 to
ed75717
Compare
|
I'll do the rebase after #3545 has been merged |
|
Build succeeded.
|
|
seems that the CI of Windows is still not happy with fifo...working on it |
6ae8f26 to
f311ee6
Compare
|
Build succeeded.
|
6047504 to
0829e71
Compare
|
Build succeeded.
|
0829e71 to
ec76380
Compare
|
Build succeeded.
|
ec76380 to
754a911
Compare
Resolved by using separate check functions between unix and windows. I'm not sure it is ok to do this, but it seems that the |
|
Build succeeded.
|
754a911 to
ef29d86
Compare
|
Build succeeded.
|
When using a multi-container shim, the fifo of the 2nd to Nth container will not be opened when the ctx is done. This will cause an `ErrReadClosed` that can be ignored. Signed-off-by: Li Yuxuan <[email protected]>
ef29d86 to
04caf1f
Compare
|
Build succeeded.
|
|
@estesp thanks for correcting the title! I've corrected the commit title as well :) And it seems that all the CI would be happy now😃 |
|
LGTM |
When using a multi-container shim, the fifo of the 2nd to Nth container will not be opened when the ctx is done. This will cause a "closed fifo" error that can be ignored.
Signed-off-by: Li Yuxuan [email protected]