Some Github jobs suddenly registering as failed although completing successfully

Since yesterday, some of the CI jobs for the OpenBLAS project suddenly get marked as failed although the log shows them as completing normally (and the PRs triggering them had no changes relevant to the affected architecture anyway). Restarting the failed jobs does not help.
One such example is
I know there were unspecified problems at github earlier this week, but both github and travis status screens do not suggest any angoing troubles, and our travis.yml configuration has not changed in a while. Anything I can do to track this down, or work around it ?

I’ll go out on a limb and say that something that’s not reflected in the build log exited with nonzero status (not sure how that should happen), and your set -e ( is causing the build script itself to exit with nonzero.

1 Like

Thanks, I’ll give that a try - and it appears to work now (though some jobs have not finished yet)