[SERVER-42968] libfuzzer teardown tasks should be merged with compile's Created: 22/Aug/19  Updated: 29/Oct/23  Resolved: 23/Aug/19

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

Type: Task Priority: Major - P3
Reporter: Spencer Jackson Assignee: Spencer Jackson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-42753 Ensure libfuzzer evergreen tasks alwa... Closed
Related
Backwards Compatibility: Fully Compatible
Sprint: Security 2019-08-26
Participants:
Linked BF Score: 50

 Description   

The corpus artifacts of the libfuzzer evergreen task must be pushed back to S3 on completion, even if the task fails. However, YAML doesn't let us extend the set of teardown tasks that are generally available, only replace them. We require the default set, in order to inform evergreen of the set of tests we run so that they may appear in the UI.

To make this work, we need to run the libfuzzer teardown tasks unconditionally in teardown for all compile-like tasks, and ensure that they are no-ops unless running with libfuzzer



 Comments   
Comment by Githook User [ 23/Aug/19 ]

Author:

{'username': 'spencerjackson', 'email': 'spencer.jackson@mongodb.com', 'name': 'Spencer Jackson'}

Message: SERVER-42968 Merge libfuzzer tasks with those in compile group
Branch: master
https://github.com/mongodb/mongo/commit/d768cef877ff502968479905a1da8f65078841d7

Comment by Spencer Jackson [ 22/Aug/19 ]

CR: https://mongodbcr.appspot.com/492790001/publish
Evgn: https://evergreen.mongodb.com/version/5d5d5fd2e3c33104f6aad6e7

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