Turn off coveralls for POCL builds #599
Closed
Conversation
This file contains hidden or 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
|
Ah.. It still sometimes takes too much time... We can consider not running tests in POCL+gcc builds (clang builds are OK) until POCL becomes faster or just ignore it and wait for the next release of POCL which should be faster (POCL master branch is now faster than current release [0.13] or at least was because we did not have those problems before switching from master to 0.13). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
It takes a long time to run POCL builds and having coveralls in them only makes them fail due to exceeding the maximum time limit (see https://travis-ci.org/boostorg/compute/jobs/125418210). We will still have coveralls stats from AMD APP builds with gcc (OpenCL 1.2 and 2.0).