-
Type:
Build Failure
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Backup
-
Storage Engines
-
10
-
5
-
StorEng - 2024-12-24
Failures are occurring in test_incr_backup running on MacOS 14, specifically a comparison of backup files is failing:
[2024/12/10 23:09:44.712] **** iteration 9 **** [2024/12/10 23:09:44.712] Checkpoint 18 [2024/12/10 23:09:44.712] Close and reopen the connection 2 [2024/12/10 23:09:44.712] test_incr_backup: FAILED: void testutil_verify_src_backup(WT_CONNECTION *, const char *, const char *, char *)/492: system(cmp -n 18432 WT_HOME/t74-0.wt backup.src.9/t74-0.wt 8017920 8017920): Unknown error: 256 [2024/12/10 23:09:44.712] **** FAILURE [2024/12/10 23:09:44.712] To reproduce, please rerun with: test_incr_backup -S 11130491881203250245 [2024/12/10 23:09:44.712] test_incr_backup: process aborting [2024/12/10 23:09:44.712] WiredTiger Error: void __wt_abort(WT_SESSION_IMPL *), 29: aborting WiredTiger library
This ticket was spun out of WT-13786, to which the BFGs for these failures were originally (incorrectly) linked. WT-13786 describes a failure (also in test_incr_backup) which currently appears to be a seperate issue.
Using the seed parameter (11130491881203250245) from one of the BFG failures, I am frequently able to reproduce the failure on my M3 Max based MacBook Pro:
Delete_old_backups: Retain 4 Delete_old_backups: Remove backup.4, renamed to OLD.backup.4 Deleted 1 old backup cmp: EOF on WT_HOME/t74-0.wt test_incr_backup: FAILED: void testutil_verify_src_backup(WT_CONNECTION *, const char *, const char *, char *)/492: system(cmp -n 18432 WT_HOME/t74-0.wt backup.src.9/t74-0.wt 8165376 8165376): Unknown error: 256 **** FAILURE To reproduce, please rerun with: test_incr_backup -S 11130491881203250245 test_incr_backup: process aborting WiredTiger Error: void __wt_abort(WT_SESSION_IMPL *), 29: aborting WiredTiger libraryProcess finished with exit code 134 (interrupted by signal 6:SIGABRT)
On my MacBook, this test fails about 50% of the time when run from the command line and in CLion. However, I've not seen it fail in the CLion debugger, which is curious. jasmine.bi@mongodb.com has also reproduced the issue running on her MacBook Pro.