Fix travis log doesn't produce any output for more than 10 minutes #1821
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
…es in CI tests So we can avoid our tests to fail in case that the travis log doesn't produce any output for more than 10 minutes (this is a travis limitation) See also: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received
Also, we slightly modify the opencv recipe to force build the opencv recipe in CI tests so this way we will make sure that the recently applied fix works as expected for a recipe which requires a long compilation time
AndreMiras
approved these changes
May 20, 2019
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.
I saw this in the following situations:
CItests that shouldn't fail (I suspect that this is caused at times of high overload of the travis system)...like this one: https://travis-ci.org/kivy/python-for-android/builds/527925625So, in order to fix the above mentioned situations, this pr will run a background process which will print a message in travis log each 9 minutes. This background process will be killed after we make our tests.
Also we enable the
opencvrecipe forrebuild_updated_recipesin order to demonstrate that the background process introduced in here works as expected.As a side note: we also could use the travis command
travis_waitto do a similar thing as we do in this pr, but the problem of this command is that we will not get any log until we finish all the tests...Also see: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received