-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
StorEng - Defined Pipeline
-
3
Logging is always enabled in our compatibility testing. We should randomise this value to have more coverage.
Suggested changes:
diff --git a/test/evergreen/compatibility_test_for_releases.sh b/test/evergreen/compatibility_test_for_releases.sh
index 18e2742f3..978dc4c32 100755
--- a/test/evergreen/compatibility_test_for_releases.sh
+++ b/test/evergreen/compatibility_test_for_releases.sh
@@ -166,18 +166,14 @@ create_configs()
echo "huffman_key=0" >> $file_name # WT-6893 - Not supported by newer releases
echo "in_memory=0" >> $file_name # Interested in the on-disk format
echo "leak_memory=1" >> $file_name # Faster runs
- echo "logging=1" >> $file_name # Test log compatibility
echo "logging_compression=snappy" >> $file_name # We only built with snappy, force the choice
echo "rows=1000000" >> $file_name
echo "salvage=0" >> $file_name # Faster runs
echo "stress.checkpoint=0" >> $file_name # Faster runs
echo "timer=4" >> $file_name
echo "verify=1" >> $file_name
- # WT-8601 has not been backported to 4.2 and transactions are expected to be timestamped.
if [ "$branch_name" == "mongodb-4.2" ] ; then
echo "transaction.timestamps=1" >> $file_name # WT-7545 - Older releases can't do non-timestamp transactions
- else
- echo "transaction.timestamps=0" >> $file_name # WT-8601 - Timestamps do not work with logged tables
fi
# Append older release configs for newer compatibility release test