|
Author:
{'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}
Message: SERVER-38312 Don't include task id in filename for npm test output.
(cherry picked from commit 8e90b018e133641a937b6effdccd8e2d3bd9946a)
Branch: v4.0
https://github.com/mongodb/mongo/commit/7bec25e3fa07968d35924c5319d13e4bda7c8266
|
|
Author:
{'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}
Message: SERVER-38312 Don't include task id in filename for npm test output.
Branch: master
https://github.com/mongodb/mongo/commit/8e90b018e133641a937b6effdccd8e2d3bd9946a
|
|
Generated tasks need a unique name across buildvariants, otherwise if the generate task command is run on multiple build variants, the generated tasks will collide and whichever run after the 1st will fail.
|
|
david.bradford, what was the motivation for including the build variant name in the generated task name? I think in this case we can just use a non-unique filename because I'm confident in Evergreen's ability to clean up the working directory / bash's ability to truncate files, but wasn't sure if we'd see impact in other places that are more work to fix.
|
Generated at Thu Feb 08 04:48:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.