CI: disable integration tests #2062
Merged
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
Some of the tests are more often failing than passing and we stopped even checking the results. So we might as well disable the tests for now, so that it at least looks better in the README badge and PR checks. Also, we save some of Azures CPU cycles just burns energy without any gain at this point. I think in the future we can discuss bringing back some tests, or just have some examples executable as tests instead but heavily rely on the system-tests instead. The example tests added back in would be to test a few cases that cover whether things are roughly still connecting and running, however, it won't be feasible to have integration tests for all sorts of combinations of PX4 and ArduPilot versions against all of the various features because we just run into combinatorial explosion. Signed-off-by: Julian Oes <[email protected]>
13 tasks
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.
Some of the tests are more often failing than passing and we stopped even checking the results. So we might as well disable the tests for now, so that it at least looks better in the README badge and PR checks.
Also, we save some of Azures CPU cycles just burns energy without any gain at this point.
I think in the future we can discuss bringing back some tests, or just have some examples executable as tests instead but heavily rely on the system-tests instead.
The example tests added back in would be to test a few cases that cover whether things are roughly still connecting and running, however, it won't be feasible to have integration tests for all sorts of combinations of PX4 and ArduPilot versions against all of the various features because we just run into combinatorial explosion.