[#65451] [ruby-trunk - Feature #10333] [PATCH 3/1] optimize: "yoda literal" == string — ko1@...
Issue #10333 has been updated by Koichi Sasada.
ko1@atdot.net wrote:
Eric Wong <normalperson@yhbt.net> wrote:
Eric Wong <normalperson@yhbt.net> wrote:
On 2014/10/09 11:04, Eric Wong wrote:
SASADA Koichi <ko1@atdot.net> wrote:
[#65453] [ruby-trunk - Feature #10328] [PATCH] make OPT_SUPPORT_JOKE a proper VM option — ko1@...
Issue #10328 has been updated by Koichi Sasada.
[#65559] is there a name for this? — Xavier Noria <fxn@...>
When describing stuff about constants (working in their guide), you often
On 2014/10/09 20:41, Xavier Noria wrote:
On Thu, Oct 9, 2014 at 1:59 PM, Nobuyoshi Nakada <nobu@ruby-lang.org> wrote:
[#65566] [ruby-trunk - Feature #10351] [Open] [PATCH] prevent CVE-2014-6277 — shyouhei@...
Issue #10351 has been reported by Shyouhei Urabe.
[#65741] Re: [ruby-cvs:55121] normal:r47971 (trunk): test/ruby/test_rubyoptions.rb: fix race — Nobuyoshi Nakada <nobu@...>
On 2014/10/16 10:10, normal@ruby-lang.org wrote:
Nobuyoshi Nakada <nobu@ruby-lang.org> wrote:
2014-10-16 12:48 GMT+09:00 Eric Wong <normalperson@yhbt.net>:
[#65753] [ruby-trunk - Feature #10333] [PATCH 3/1] optimize: "yoda literal" == string — ko1@...
Issue #10333 has been updated by Koichi Sasada.
[#65818] [ruby-trunk - Feature #10351] [PATCH] prevent CVE-2014-6277 — shyouhei@...
Issue #10351 has been updated by Shyouhei Urabe.
[ruby-core:65357] Re: [ruby-trunk - Bug #10313] [Open] Randomly build failure on Travis container.
shibata.hiroshi@gmail.com wrote: > We tested ruby trunk every commits, but it failed randomly with linux container on travis. > > build log is here: https://s3.amazonaws.com/archive.travis-ci.org/jobs/36822816/log.txt > > It's caused by fadvice(2). it details is following: > > ``` > # make test-all > TestIO#test_advise: > Errno::EINVAL: Invalid argument - /tmp/test_io20141001-24823-10d6utc (0, 0, willneed) This seems to be a problem on old Linux kernels (2.6.32 from what Travis log says) and tmpfs. Which Linux kernels do you hit successful builds on? Are they using tmpfs for /tmp? kosaki fixed it in Linux kernel commit 3d3727cdb07ff17ddc3c551ef8d03d37b60a0372 "mm, fadvise: don't return -EINVAL when filesystem cannot implement fadvise()" (but old kernels will be around for many more years) > Is there workaround this? I think we need to accept EINVAL in our tests, unless there is a way to force the test to run on a regular FS.