[SERVER-44986] Blacklist incompatible tests from replica_sets_multiversion suite Created: 06/Dec/19  Updated: 29/Oct/23  Resolved: 10/Dec/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 4.3 Required
Fix Version/s: 4.3.3

Type: Bug Priority: Major - P3
Reporter: Jason Chan Assignee: Jason Chan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2019-12-16
Participants:
Linked BF Score: 50

 Description   

log_secondary_oplog_application.js test times outs specifically when assigned a "last-stable" (v4.2) secondary because the log message that the secondary specifically waits for has changed between the versions so we fail the assert.soon.
IE. The test expects the logs to contain "applyOplogEntryOrGroupedInserts - fail point hangAfterRecordingOpApplicationStartTime enabled" but instead the on v4.2, the secondary will be printing "syncApply - fail point hangAfterRecordingOpApplicationStartTime enabled"..

recover_prepared_txn_with_multikey.js should be tagged multiversion_incompatible since it restarts nodes in the test.

apply_ops_create_indexes.js should be tagged with requires_fcv_44 since enableTwoPhaseIndexBuilds is not available on v4.2.

read_operations_during_rollback.js should have the requires_fcv_44 tag since we don't log state transition metrics in v4.2.

startup_without_fcv_document_succeeds_if_initial_sync_flag_set.js should be tagged with multiversion_incompatible since it checks that the latest fcv document was replicated to the secondary.

uninitialized_fcv_access.js should be tagged multiversion_incompatible since it asserts a specific FCV version.

transient_txn_error_label.js should be tagged multiversion_incompatible since it uses ShardingTest which is not supported by the replica_sets_multiversion test suite.

initial_sync_survives_network_error.js should be tagged requires_fcv_44 since it uses a failpoint not available in v4.2.

drop_databases_two_phase.js should be tagged requires_fcv_44 because behavior from SERVER-43352 will not be backported to v4.2.

initial_sync_fcv.js should be tagged multiversion_incompatible since it tests behavior around different FCV's.

tla_plus_trace_checking.js should be tagged requires_fcv_44 because it makes use of a failpoint not available in v4.2.

dbhash_system_collections.js should be tagged requires_fcv_44 since SERVER-43045 will not be backported.

noop_writes_wait_for_write_concern_fcv.js should be tagged multiversion_incompatible since it tests behavior on both FCVs.

reconstruct_prepared_transactions_initial_sync_index_build.js should be tagged requires_fcv_44 since enableTwoPhaseIndexBuilds is not available on v4.2.

rollback_prepare_transaction.js should be tagged requires_fcv_44 since SERVER-42639 won't be backported.

no_disconnect_on_stepdown.js should be tagged requires_fcv_44 since we don't log state transition metrics in v4.2.

transient_txn_error_labels_with_write_concern.js should be tagged multiversion_incompatible since it uses ShardingTest which is not supported by the replica_sets_multiversion test suite.

initial_sync_test_fixture_test.js should be tagged requires_fcv_44 since the test relies on synchronization points added by SERVER-44014 which are not available on v4.2.

reconstruct_prepared_transactions_initial_sync_change_oldest_active_txn_timestamp.js should be tagged requires_fcv_44 since the test relies on a failpoint not available on v4.2.

drop_oplog_should_fail_if_storage_engine_supports_replSetResizeOplog_command.js should be tagged multiversion_incompatible since standalones are not supported in multiversion testing.



 Comments   
Comment by Githook User [ 10/Dec/19 ]

Author:

{'name': 'Jason Chan', 'username': 'jasonjhchan', 'email': 'jason.chan@mongodb.com'}

Message: SERVER-44986 Blacklist incompatible tests from replica_sets_multiversion suite
Branch: master
https://github.com/mongodb/mongo/commit/90faa089a975c5879bb2f9eeb851895ac0cc5bb6

Generated at Thu Feb 08 05:07:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.