From 76f9bc7e660c6b46b9f80712d415151f32280e2d Mon Sep 17 00:00:00 2001 From: Takashi Kokubun Date: Wed, 20 Oct 2021 21:57:48 -0700 Subject: [PATCH] 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. --- .travis.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) 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