Major - P3 The wiredtiger-compatibility job captured an assertion failure on 'kodkod' that an unexpected starting record number was detected while verifying internal pages of an older version (WT 3.0.0) of data files. 'r2' here maps to WT '3.0.0' release.
http://build.wiredtiger.com:8080/job/wiredtiger-compatibility/720/console
Starting to verify URI for "r2" branch/release ... Verifying file:wt using ../build_posix.r2/wt binary Verifying file:wt using ../build_posix.develop/wt binary [1545353672:489874][12066:0x7fc3edef4740], t, file:wt, WT_SESSION.verify: __verify_tree, 525: the starting record number in entry 46 of the column internal page at [1762304-1774592, 12288, 1005888311] is 1639 and the expected starting record number is 1640: WT_ERROR: non-specific WiredTiger error [1545353672:490354][12066:0x7fc3edef4740], t, file:wt, WT_SESSION.verify: __verify_ckptfrag_chk, 567: checkpoint ranges never verified: 111 [1545353672:490536][12066:0x7fc3edef4740], t, file:wt, WT_SESSION.verify: __verify_filefrag_chk, 474: file ranges never verified: 110 wt: session.verify: file:wt: WT_ERROR: non-specific WiredTiger error