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

Core dump fired for larger timestamp size testing

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Storage Engines 2018-11-19

      A core dump fired while running wiredtiger-test-timestamp-size job on 'aws-build-test2' machine, with timestamp size configured as 31.  
      http://build.wiredtiger.com:8080/job/wiredtiger-test-timestamp-size/456/

      + cd build_posix/
+ ../configure CFLAGS=-ggdb --with-timestamp-size=31 --enable-silent-rules --enable-strict --enable-diagnostic --enable-python --disable-static --enable-snappy
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
...
test_timestamp11.test_timestamp11.test_timestamp_range: 0.04 seconds
test_timestamp04.test_timestamp04.test_rollback_to_stable -s 0 (nolog.col_fix): 4.64 seconds
/tmp/jenkins2833560981165338605.sh: line 9: 10400 Aborted                 (core dumped) env LD_LIBRARY_PATH=.libs python ../test/suite/run.py -v 4 timestamp*
Build step 'Execute shell' marked build as failure

      The job re-ran on the same machine and cleared the build directory, so we don't have the core file and environment context saved.

            Assignee:
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Reporter:
            luke.chen@mongodb.com Luke Chen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: