[SERVER-24848] Replace non-customized asserts in concurrency (FSM) workloads Created: 30/Jun/16  Updated: 06/Dec/22  Resolved: 11/May/20

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Minor - P4
Reporter: Kamran K. Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Won't Fix Votes: 0
Labels: stm, tig-concurrency
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Tooling & Methods
Participants:

 Description   

There are a few workloads that use the native assertion helpers instead of assertAlways/assertWhenOwnColl/assertWhenOwnDB:

count.js:            assert.gt(high, low);
remove_and_bulk_insert.js:            assert.writeOK(bulk.execute());
update_and_bulk_insert.js:            assert.writeOK(bulk.execute());

These assertions should be replaced to prevent test failures when workloads are composed together.



 Comments   
Comment by Ryan Timmons [ 11/May/20 ]

Closing as wont-fix to indicate that there is currently no intention of doing this. Please re-open if there is priority for this. Perhaps this change could self-service by an appropriate server team if this is necessary rather than having to go thru the STM prioritization queue.

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