[#119637] Behavior of raising from rescue blocks when multiple rescue blocks exist — Rodrigo Rosenfeld Rosas via ruby-core <ruby-core@...>
Hello, I couldn't find any documentation about the subject, so I thought
3 messages
2024/10/29
[ruby-core:119371] [Ruby master Bug#20773] CI of RHEL8 and Amazon Linux 2 are failed from Sep 26th
From:
"hsbt (Hiroshi SHIBATA) via ruby-core" <ruby-core@...>
Date:
2024-10-01 00:57:46 UTC
List:
ruby-core #119371
Issue #20773 has been updated by hsbt (Hiroshi SHIBATA). Status changed from Open to Closed https://github.com/ruby/ruby/pull/11736 fixed this. ---------------------------------------- Bug #20773: CI of RHEL8 and Amazon Linux 2 are failed from Sep 26th https://bugs.ruby-lang.org/issues/20773#change-109984 * Author: hsbt (Hiroshi SHIBATA) * Status: Closed * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- RHEL8 and Amazon Linux 2 are failed with `Cannot allocate memory - fork(2)` from Sep 26th. * http://rubyci.s3.amazonaws.com/rhel8/ruby-master/log/20240926T093004Z.fail.html.gz * http://rubyci.s3.amazonaws.com/amazon2/ruby-master/log/20240926T033004Z.fail.html.gz I'm not sure what's the root cause yet. Amazon Linux 2 is resolved with swapon by @mame. These are strange to increase to usage of memory only for some old distribution. -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/