Hi, I’ve noticed that sourceing a script that’s supposed to fail and surrounding it with travis_retry under Windows falsely makes the build successful. Here is a (correctly) failing build: https://travis-ci.org/DanySK/travis-testing-playground/builds/645951337?utm_medium=notification&utm_source=em…

I’ve merged the PR. This allows some reasonable workaround for the unexpected result. Since we are unable to overcome the errexit issue, I’ll advise you to concoct your own mechanism to deal with the error(s) inside your own sourced file.

Travis_retry on windows does not make the build fail

Environments Windows

BanzaiMan February 4, 2020, 8:22pm 5

I thought I knew a decent amount about bash.

1 Like

Topic		Replies	Views
Builds are failing with truncated logs when errexit is used Travis CI Discussions & Feedback	2	822	May 21, 2020
Build shows as successful even though the sole job failed Travis CI Discussions & Feedback android	5	1400	October 27, 2020
Travis CI macOS job stuck macOS build-env , bug	2	898	February 21, 2019
Log are truncated when my script exits abnormally Travis CI Discussions & Feedback	3	1212	November 11, 2019
Build fails with no obvious reason macOS	10	2334	January 14, 2019

Travis_retry on windows does not make the build fail

Related topics