agorrod The Jenkins job http://mjc.homeunix.org:8180/job/wiredtiger-compat-develop/295/ failed. The reason is that the new lsm_manager configuration string breaks backward compatibility. I think it is just coincidence those tests didn't fail until now and test/format randomly did not choose LSM until this run.

The three compatibility tests test forward and backward compatibility of both databases and tables. So, in compat-develop, we create the database in the current code, and the run wt verify on the homedir using wt from the last release. That is failing because the current code is writing lsm_manager=... into the WiredTiger.basecfg file and the old wt code does not handle that.

Will forward compatibility now be broken with the recent removal of merge_threads? That information was stored in the metadata for each LSM table, right? Will the current code be able to read the old metadata and handle that (or ignore it) now that the support for merge_threads per table was removed?

I have saved a tarball of the failure on plenty in ~jenkins/jenkins/wiredtiger-compat-develop/failure.295.tgz (just in case another run comes along and blows the existing workspace away).