[SERVER-47254] Evergreen interprets adding a new test as deleting a new test and doesn't generate burn in tests Created: 01/Apr/20  Updated: 06/Dec/22  Resolved: 03/Apr/20

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

Type: Bug Priority: Major - P3
Reporter: Matthew Saltz (Inactive) Assignee: [DO NOT ASSIGN] Backlog - Decision Automation Group (DAG) (Inactive)
Resolution: Duplicate Votes: 0
Labels: tig-burnin
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Decision Automation Group
Operating System: ALL
Participants:

 Description   

In this patch build I added a new jstest which I would expect to get run in burn_in_tests, but it seems like burn_in_tests_gen interpreted it as removing the test instead of adding it:

[2020/03/31 20:07:34.537] [2020-03-31 20:07:34,537 - buildscripts.patch_builds.change_data - DEBUG] 2020-03-31 20:07.34 deleted files                  diff=index diff files={'jstests/sharding/shard_removal_triggers_catalog_cache_invalidation.js'}

Which led to no burn_in_tests getting run.

Note that this was in 4.2, I don't know if the issue is on all branches.



 Comments   
Comment by David Bradford (Inactive) [ 03/Apr/20 ]

I'm going to backport SERVER-43732 to 4.2, which should resolve this issue.

Comment by David Bradford (Inactive) [ 02/Apr/20 ]

This looks like SERVER-43732. It should be fixed on master and v4.4. We can look into backporting it to 4.2.

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