Test suite passes on Travis-CI #7
Open
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
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.
Note: Travis-CI needs to be enabled by the admin of each repository. I've done so for uwiger/rvi_core
Amended .travis.yml to collect more data from failing test suites.
This made it clear that the bluetooth components were causing problems.
To be able to disable bluetooth (adding {remove_apps, [bt, dlink_bt] in the config), I removed these apps (and others) from the rvi_core 'applications' list, and instead introduced a system of awaiting/announcing components using gproc:reg/1 and gproc:await/1. See rvi_server.erl