workaround bad file descriptor issue happened in postprocess #4013
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
environment clean up Signed-off-by: chunfuwen <[email protected]>
nanli1
approved these changes
Nov 1, 2024
chloerh
reviewed
Nov 11, 2024
|
The bad file descriptor issue in postprocess has been fixed in #4001. And it did not appear in 103lts branch. Maybe we can close this PR. |
|
I agree with @cliping - This should not be necessary anymore as we run our tests now with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In recent tp-libvirt testing, lots of case false warning failure happened due to ungraceful handling of postprocess cleanup in env_process.py.
Here it is workaround solution, just output error message instead of raising exception