Hello, our team members noticed today that builds configured with “matrix: / allow_failures” list no longer ignore (or specially mark up in build results) the build items while build issues should not fail the build.
https://travis-ci.org/github/42ity/fty-common/builds/658744371/config?utm_medium=notification&utm_source=github_status (line 206) shows the config used in the failing build https://travis-ci.org/github/42ity/fty-common/builds/658744371?utm_source=github_status&utm_medium=notification (item 344.10 in the list failed, and no items allowed a failure as Travis decided). A re-build of the PR did not help.
Earlier builds worked as expected, e.g. 343 : https://travis-ci.org/github/42ity/fty-common/builds/657780343?utm_medium=notification&utm_source=github_status
Curiously, some later builds were scheduled by cron but failed with “ERROR: This build could not be run. Reason: invalid_config” e.g. https://travis-ci.org/github/42ity/fty-common/builds/660656507?utm_medium=notification&utm_source=github_status but were parsed for results as having the expected block of allowed-failure scenarios.
At this time another build scheduled by cron is pending: https://travis-ci.org/github/42ity/fty-common/builds/663533613?utm_medium=notification&utm_source=github_status so I hope this was an intermittent hiccup or quickly fixed issue pushed to travis codebase