There was a Jenkins test failure over night:
http://build.wiredtiger.com:8080/job/wiredtiger-test-format-stress-sanitizer/2529/console
The interesting output is:
t: session.verify: file:wt: post-ops verify: Device or resource busy
The particular config is:
############################################ # RUN PARAMETERS ############################################ auto_throttle=1 firstfit=0 bitcnt=3 bloom=0 bloom_bit_count=21 bloom_hash_count=31 bloom_oldest=0 cache=1 checkpoints=1 checksum=uncompressed chunk_size=6 compaction=1 compression=zlib data_extend=0 data_source=file delete_pct=12 dictionary=0 evict_max=5 file_type=variable-length column-store backups=0 huffman_key=0 huffman_value=0 insert_pct=8 internal_key_truncation=1 internal_page_max=14 isolation=read-committed key_gap=20 key_max=39 key_min=28 leak_memory=0 leaf_page_max=17 logging=0 lsm_worker_threads=4 merge_max=8 mmap=1 ops=100000 prefix_compression=1 prefix_compression_min=8 repeat_data_pct=64 reverse=0 rows=100000 runs=1 split_pct=57 statistics=0 threads=1 timer=0 value_max=268 value_min=16 wiredtiger_config= write_pct=57 ############################################
The console goes on to report memory leaks from Berkeley DB, but I suspect that is a result of exiting aggressively.
- is related to
-
WT-1508 Avoid EBUSY returns to verify and salvage caused by checkpoints
- Closed
-
- Closed
-
- Closed
-
- Closed
- related to
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed