luke.chen, I was reviewing the compiler tests I'm still regularly running vs. the ones Jenkins runs, and there are a few configurations I'm testing we don't regularly test as part of the Jenkins wiredtiger-pull-request-compilers job.

If we could test these somewhere, then I could retire that part of my separate testing.

My list includes:

• --disable-crc32-hardware
• --enable-leveldb
• --enable-leveldb=basho
• --enable-leveldb=hyper
• --enable-leveldb=rocksdb
• --enable-python
• --enable-tcmalloc
• --java
• --with-spinlock=gcc
• --with-spinlock=pthread
• --with-spinlock=pthread_adaptive

The compiler build currently takes 11 minutes, so it's not the slow part of a PR build.

But, I don't see much point in testing any of these options on every build, once a week on the develop branch would be more than sufficient.

We could probably drop the LevelDB variants too, I doubt they're still interesting to anyone.