[SERVER-38312] Unable to run jstestfuzz* tasks on variants with long names Created: 29/Nov/18  Updated: 29/Oct/23  Resolved: 29/Nov/18

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.0.5, 4.1.6

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Max Hirschhorn
Resolution: Fixed Votes: 0
Labels: tig-evgconfig
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Problem/Incident
is caused by SERVER-38116 Update fuzzer tasks to use generate.t... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Sprint: STM 2018-12-17
Participants:
Story Points: 1

 Description   

The fuzzer's self-tests run before the jstestfuzz* tasks and writes the output to a filename that includes the task id. After the changes from 18452b9 as part of SERVER-38116, this leads too long of a filename.

npm test > npm_test-${task_id}.log 2>&1

https://evergreen.mongodb.com/task_log_raw/mongodb_mongo_master_enterprise_rhel_62_64_bit_majority_read_concern_off_jstestfuzz_interrupt_replication_0_enterprise_rhel_62_64_bit_majority_read_concern_off_patch_41c44d02cf39ef581888bed68c547e4ed9b5a323_5bff8490e3c33123cb9e7dfa_18_11_29_06_19_05/0?type=T

[2018/11/29 06:56:17.137] npm test > npm_test-mongodb_mongo_master_enterprise_rhel_62_64_bit_majority_read_concern_off_jstestfuzz_interrupt_replication_0_enterprise_rhel_62_64_bit_majority_read_concern_off_patch_41c44d02cf39ef581888bed68c547e4ed9b5a323_5bff8490e3c33123cb9e7dfa_18_11_29_06_19_05.log 2>&1
[2018/11/29 06:56:17.137] sh: line 16: npm_test-mongodb_mongo_master_enterprise_rhel_62_64_bit_majority_read_concern_off_jstestfuzz_interrupt_replication_0_enterprise_rhel_62_64_bit_majority_read_concern_off_patch_41c44d02cf39ef581888bed68c547e4ed9b5a323_5bff8490e3c33123cb9e7dfa_18_11_29_06_19_05.log: File name too long



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

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

Comment by Githook User [ 29/Nov/18 ]

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

Comment by David Bradford (Inactive) [ 29/Nov/18 ]

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.

Comment by Max Hirschhorn [ 29/Nov/18 ]

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.