[SERVER-32931] System failure of burn_in_tests on v3.4 when no tests have been changed Created: 26/Jan/18  Updated: 29/Oct/23  Resolved: 30/Jan/18

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

Type: Bug Priority: Major - P3
Reporter: Yves Duhem Assignee: Yves Duhem
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: TIG 2018-02-12
Participants:
Linked BF Score: 0

 Description   

After the backport of SERVER-30565 to the v3.4 branch the burn_in_tests task has been failing when no changed tests are found.
This is due to a difference in behavior of burn_in_tests.py between the v3.4 branch and more recent branches.
In v3.4 burn_in_tests.py does not write the JSON output file when no changed tests are found causing the following cp of the file to fail, while the more recent versions do produce a file.



 Comments   
Comment by Githook User [ 30/Jan/18 ]

Author:

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

Message: SERVER-32931 burn_in_tests.py creates empty report if there are no new or modified tests

(cherry picked from commit e351e669b05a82c0aea1d71538efc0cd0bf94dc4)
Branch: v3.4
https://github.com/mongodb/mongo/commit/db04f59b03186f4662b4fb8dceeffa6ff79874eb

Comment by Yves Duhem [ 26/Jan/18 ]

max.hirschhorn, yes, backporting that commit would fix the issue.

Comment by Max Hirschhorn [ 26/Jan/18 ]

yves.duhem, is this ticket about backporting the changes from e351e6 as part of SERVER-28784 to the 3.4 branch?

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