[SERVER-21969] Long running concurrency tests can time out Created: 21/Dec/15  Updated: 20/Jan/16  Resolved: 20/Jan/16

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

Type: Improvement Priority: Major - P3
Reporter: Jonathan Abrahams Assignee: DO NOT USE - Backlog - Test Infrastructure Group (TIG)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-22100 memory pressure from find/getMore buf... Closed
Related
Backwards Compatibility: Fully Compatible
Participants:
Linked BF Score: 0

 Description   

A Windows DEBUG concurrency test timed out after 2 hours, fsm_all_replication - mmapv1 (https://logkeeper.mongodb.org/build/567463a09041306f2400f00c/test/567463a0be07c46976010411)

The following tests ran more than 10 minutes:

  • remove_and_bulk_insert.js 845092 ms - 14 minutes
  • update_and_bulk_insert.js 2758568 ms - 46 minutes
  • create_index_background.js 913785 ms - 15 minutes

The same tests on Windows DEBUG concurrency fsm_all_replication - wiredTiger (https://logkeeper.mongodb.org/build/5674638e9041306f2400efef/test/5674638ebe07c469760103f4):

  • remove_and_bulk_insert.js 786405 ms - 13 minutes
  • update_and_bulk_insert.js 793241 ms - 13 minutes
  • create_index_background.js 1061733 ms - 17 minutes

These tests should be sped up, run in a slow suite or possibly be blacklisted for certain platforms.

Perhaps a new slow suite should be considered.



 Comments   
Comment by Kamran K. [ 20/Jan/16 ]

I believe this is a duplicate of SERVER-22100.

Generated at Thu Feb 08 03:59:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.