Add tests to conda-forge job #3264
Closed
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
|
It seems that there is some sort of cross-talking, so even if after one round I disable all failing test, and the following round more test fail. So probably for the moment it is a better idea just to run a few specified tests. |
|
Ok, by running just the |
|
Apparently the problem in |
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 conda-forge/gazebo-feedstock#148 we debugged quite a tricky issue that only appeared at runtime. To avoid having problems like this in the future, I tried to enable tests (skipping the one that are currently failing) in the conda-forge job.
As the conda-forge CI job is already quite slow (~1 hour and 15 minutes), we can also think of changing the job to run the tests only on a given schedule, but for the time being I just implemented the simplest solution.