Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-3249

Unit test test_readonly fails as it is unable to open WiredTiger.lock

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • WT2.9.2, 3.2.13, 3.4.4, 3.5.6
    • None
    • None
    • Storage 2017-04-17

    Description

      The following unit test run has failed:
      http://build.wiredtiger.com:8080/job/wiredtiger-test-spinlock/3532

      The error reported is:

      [1490994372:545452][39815:0x7fe893d27700], test_readonly01.test_readonly01.test_readonly(no_basecfg.readonly.logging.table-row), wiredtiger_open: ./WiredTiger.lock: handle-open: open: Permission denied
      [1490994372:547676][39815:0x7fe893d27700], test_readonly01.test_readonly01.test_readonly(no_basecfg.readonly.logging.table-row), txn-recover: Read-only database needs recovery: WT_RUN_RECOVERY: recovery must be run to continue
      [1490994372:547718][39815:0x7fe893d27700], test_readonly01.test_readonly01.test_readonly(no_basecfg.readonly.logging.table-row), txn-recover: Recovery failed: WT_RUN_RECOVERY: recovery must be run to continue
      

      Testing shows that this was likely introduced along side WT-3243 as it reproduces on a 1-25 basis on the commit including the WT-3243, but does not occur on that commits parent.

      Command I have been using to reproduce is:

      cd build_posix
      ../configure --enable-python --with-spinlock=gcc --enable-strict
      make all -j8
      for i in {1..100}; do env LD_LIBRARY_PATH=.libs python ../test/suite/run.py -v 2 -j 4 test_readonly01.test_readonly01.test_readonly; done
      

      Attachments

        Activity

          People

            sue.loverso@mongodb.com Susan LoVerso
            david.hows David Hows
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: