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

Random abort should wait until record files exist before starting timer

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.9, 4.0.3, 4.1.3, WT3.2.0
    • Affects Version/s: None
    • Component/s: None
    • Storage Engines 2018-08-27, Storage Engines 2018-09-10

      test_random_abort with in-memory logging aborted failing to open records-0 file on 'tinderbox'. 

      http://build.wiredtiger.com:8080/job/wiredtiger-test-recovery-stress/48622/console

      ../configure CFLAGS="-ggdb" --enable-strict --enable-diagnostic --with-builtins=lz4,snappy,zlib --with-berkeleydb=$bdb
      ...
      + ./test_random_abort -m
      Parent: Compatibility false in-mem log true
      Parent: Create 6 threads; sleep 10 seconds
      Kill child
      Open database, run recovery and verify content
      test_random_abort: FAILED: fopen: records-0: No such file or directory
      process aborting
      /tmp/jenkins2570111138612025302.sh: line 17: 63296 Aborted                 (core dumped) ./test_random_abort -m
      + cleanup
      + status=134

      Backtrace:

      (gdb) bt
      #0  0x00007f2a48f919fb in raise () from /lib64/libc.so.6
      #1  0x00007f2a48f93800 in abort () from /lib64/libc.so.6
      #2  0x0000000000404253 in testutil_die (e=2, fmt=0x5a98d0 "fopen: %s") at ../../../test/utility/misc.c:62
      #3  0x0000000000403d03 in main (argc=0, argv=0x7fff434179f8) at ../../../test/csuite/random_abort/main.c:382 

       

            Assignee:
            sue.loverso@mongodb.com Susan LoVerso
            Reporter:
            luke.chen@mongodb.com Luke Chen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: