[SERVER-42071] notary client errors should not be system-failures Created: 03/Jul/19  Updated: 29/Oct/23  Resolved: 17/Jul/20

Status: Closed
Project: Core Server
Component/s: Build
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Task Priority: Major - P3
Reporter: Sam Kleinman (Inactive) Assignee: Annie Black
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4, v4.2, v4.0, v3.6
Sprint: Evergreen 2020-04-06, Evergreen 2020-04-20, Evergreen 2020-05-04, Evergreen 2020-05-18, Evergreen 2020-06-01, Evergreen 2020-07-27
Participants:
Story Points: 2

 Description   

in cases like this: https://evergreen.mongodb.com/task/mongodb_mongo_v4.0_enterprise_rhel_70_64_bit_push_5f93fc9db3a3475dd2c7543b9f1e1179e6f9065f_19_06_14_13_51_46 notary client errors obscured a different issue in evergreen.

this is a one line change (adding type: "test" on line 2437, the hard part is figuring what kind of error (test=red or setup=lavender) we want this to be. I think it shouldn't be a system failure, as this will probably make it harder to diagnose other issues.



 Comments   
Comment by Githook User [ 17/Jul/20 ]

Author:

{'name': 'Annie Black', 'email': 'annie.black@mongodb.com'}

Message: SERVER-42071 mark notary client errors as failed
Branch: master
https://github.com/mongodb/mongo/commit/4aa1a5d5d49e13d1080b1d73eb4ba79b49e1acb2

Comment by Kelsey Schubert [ 05/Feb/20 ]

I think test is fine. I'm not sure that lavender vs. red in this case is a useful distinction.

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