Fix Travis CI Shell Options #2490
Conversation
Signed-off-by: Schuyler Eldridge <schuyler.eldridge@ibm.com>
Disables immediate failure when running travis_wait methods. These tests need to keep going even if they fail to do things like print out the log. Signed-off-by: Schuyler Eldridge <schuyler.eldridge@ibm.com>
seldridge
force-pushed
the
unset-travis-variable
branch
from
ea98671 to
bb2ddb6
Compare
Signed-off-by: Schuyler Eldridge <schuyler.eldridge@ibm.com>
|
@richardxia: I have no idea what that failure was before I pushed. I assume that's spurious. I did notice that the log for the JTAG tests is large (>500MiB). I added a commit that turns off |
|
Yeah, I agree that it's probably spurious, since I can't see why any of the changes here would cause that test to specifically fail. |
|
Ping @richardxia. Okay to merge this? (I technically have the power to do it, but that seems inappropriate.) |
Yep, I think the build was still running when I left my review, but I can hit the merge button now. Thanks again! |
|
Need that Mergify |
This fixes two issues when using the new regression scripts on Travis infrastructure:
travis_setup_env.bashmay have an undefined variableTRAVIS_ENABLE_INFRA_DETECTION. This script needs to continue past this and have unset variable checking disabled.travis_wait.bashis written such that it needs to continue after the first failure to do useful things like print out the log of execution.Related issue: None.
Type of change: bug fix
Impact: no functional change
Development Phase: implementation
Release Notes
None.