[SERVER-42377] burn_in_tests looks at incorrect commit to compare against Created: 12/Jul/19  Updated: 29/Oct/23  Resolved: 24/Jul/19

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.2.0-rc5, 4.3.1

Type: Bug Priority: Major - P3
Reporter: Maria van Keulen Assignee: David Bradford (Inactive)
Resolution: Fixed Votes: 0
Labels: tig-burnin
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.2, v4.0
Sprint: DAG 2019-07-29
Participants:
Linked BF Score: 0
Story Points: 2

 Description   

I pushed a change that I expected to have a one-off burn_in_tests failure, but it failed in a few commits (see BF-13954) because the same tests were still being run. Here is the task for the commit. It looks like burn_in_tests is looking at the wrong commit to compare against to find changed tests.



 Comments   
Comment by Githook User [ 24/Jul/19 ]

Author:

{'name': 'David Bradford', 'username': 'dbradf', 'email': 'david.bradford@mongodb.com'}

Message: SERVER-42377: Update how burn_in_tests determines tests to run.
Branch: v4.2
https://github.com/mongodb/mongo/commit/e324999f4444483c01fee1a7233bcfd31df2aed0

Comment by David Bradford (Inactive) [ 24/Jul/19 ]

On master, I recently changed how burn_in_tests determined what to diff against. That change fixes this problem, but is is also make changes to things that are only on master. I'm going to use this to backport the relevant parts of that change to older releases (since the actual BF is on the 4.2 branch).

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