diff options
| author | Takashi Kokubun <[email protected]> | 2021-10-20 21:57:48 -0700 |
|---|---|---|
| committer | Takashi Kokubun <[email protected]> | 2021-10-20 21:57:49 -0700 |
| commit | 76f9bc7e660c6b46b9f80712d415151f32280e2d (patch) | |
| tree | 78ec72380bfbeaa964b3187319e25c885d8130bf | |
| parent | 582316870639fc13e77a63c7704beacb2686da7b (diff) | |
Reduce the amount of false positive notifications
While f6048e592c520e20ba498ba4d553f07f02213a61 tried to approach the
instability mentioned there, unfortunately the Travis arm32 environment
seems unstable by itself. I already saw 2 different failures in the last
4 builds:
https://app.travis-ci.com/github/ruby/ruby/jobs/544382885
https://app.travis-ci.com/github/ruby/ruby/jobs/544361370
Let's revisit this when this kind of thing stops happening.
| -rw-r--r-- | .travis.yml | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/.travis.yml b/.travis.yml index c47de4b80a..eb816b815b 100644 --- a/.travis.yml +++ b/.travis.yml @@ -125,7 +125,11 @@ matrix: - <<: *ppc64le-linux - <<: *s390x-linux allow_failures: - # - name: arm32-linux + # We see multiple errors indicating errors on the Travis environment itself in a short while: + # https://app.travis-ci.com/github/ruby/ruby/jobs/544382885 + # https://app.travis-ci.com/github/ruby/ruby/jobs/544361370 + # It's not a fault of Ruby's arm32 support but just Travis arm32 seems unsable. + - name: arm32-linux # - name: arm64-linux # We see "Some worker was crashed." in about 40% of recent ppc64le-linux jobs # e.g. https://app.travis-ci.com/github/ruby/ruby/jobs/530959548 |