From: normalperson@... Date: 2014-10-02T03:12:08+00:00 Subject: [ruby-core:65358] [ruby-trunk - Bug #10313] Randomly build failure on Travis container. Issue #10313 has been updated by Eric Wong. 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. ---------------------------------------- Bug #10313: Randomly build failure on Travis container. https://bugs.ruby-lang.org/issues/10313#change-49164 * Author: Hiroshi SHIBATA * Status: Open * Priority: Normal * Assignee: * Category: * Target version: * ruby -v: 2.2.0 * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN ---------------------------------------- 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) # make test-rubyspec IO#advise supports the willneed advice type ERROR Errno::EINVAL: Invalid argument - (0, 0, willneed) ``` Is there workaround this? -- https://bugs.ruby-lang.org/