[testing] having crash text definitely means the test is not stable. #17455
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
dothebart
force-pushed
the
bug-fix/tcpdump-crash-prevails
branch
from
f869966
to
15341d5
Compare
…rangodb/arangodb into bug-fix/tcpdump-crash-prevails
…-fix/tcpdump-crash-prevails
…-fix/tcpdump-crash-prevails
KVS85
approved these changes
Nov 17, 2022
…-fix/tcpdump-crash-prevails
fceller
approved these changes
Nov 17, 2022
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.
Scope & Purpose
as we saw with
arangodb/oskar#448
we would rather like to have a testrun even if we fail to launch the sniffer.
However, in case of anything in the debugger-message, we must fail.