Temporarily disable indirect and attach cases due to breaking CI #86
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.
I removed the new tests in run.py since it broke the CI and blocked any CI test from passing. I don't know anything about Jenkins and probably don't have access to it so I need to discuss with @jjhursey. I also need to figure out how to tell the run.py script where to find its files, master or elsewhere.
Removing these two tests should put the debug CI back to the working state it was in yesterday.
I alo looked at the log for PR 2153 and it looks like the testcase wrote a line to stderr at the start of the run and threw off the sequence number for everything else. Also, it looks like the LAUNCH_COMPLETE event label got changed to READY-FOR-DEBUG by another change in a different pull request, so I need to look at that, both on Monday.
Signed-off-by: David Wootton [email protected]