[SERVER-27653] Blacklist Concurrency suite in burn_in_tests Created: 12/Jan/17  Updated: 05/Apr/17  Resolved: 13/Jan/17

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

Type: Improvement Priority: Major - P3
Reporter: Jonathan Abrahams Assignee: Jonathan Abrahams
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-24695 burn_in_tests.py should have a mechan... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.4
Sprint: TIG 2017-01-02
Participants:
Linked BF Score: 0

 Description   

The burn_in_tests cannot run the concurrency suite, because when run simultaneously they can cause build failures. Also, presently, changes to concurrency workload files are not directly associated to tasks and would not trigger burn_in_tests to run. Only changes to the fsm_all_* runners would trigger burn_in_tests.



 Comments   
Comment by Githook User [ 17/Jan/17 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-27653 Blacklist Concurrency test runners in burn_in_tests

(cherry picked from commit 72f9bd42dfc56921c5a92d7e5ed00075e132b75b)
Branch: v3.4
https://github.com/mongodb/mongo/commit/30c8923a354ea47fbea6cf68c69d2043899384a9

Comment by Githook User [ 13/Jan/17 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-27653 Blacklist Concurrency test runners in burn_in_tests
Branch: master
https://github.com/mongodb/mongo/commit/72f9bd42dfc56921c5a92d7e5ed00075e132b75b

Comment by Max Hirschhorn [ 13/Jan/17 ]

This should just blacklist the concurrency tasks which run against a replica set or sharded cluster.

jonathan.abrahams, I think it would be useful to have the burn_in_tests.py script not run any of the fsm_all*.js runners to avoid potential issues from attempting to run both fsm_all.js and fsm_all_simultaneous.js concurrently (as well as concurrently with other changes tests) since it runs with --jobs > 1 regardless of the underlying task definitions.

Comment by Jonathan Abrahams [ 13/Jan/17 ]

This should just blacklist the concurrency tasks which run against a replica set or sharded cluster.

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