0
0
mirror of https://github.com/mongodb/mongo.git synced 2024-11-22 04:59:34 +01:00

SERVER-85780 Increase timeout and decrease number of generated files in the timeseries fuzzer (#18462)

GitOrigin-RevId: b38cc8dd000c2bb71707353fb70d489e106b8969
This commit is contained in:
Gil Alon 2024-01-30 19:45:37 -05:00 committed by MongoDB Bot
parent d5a6160830
commit f90c33527b
2 changed files with 8 additions and 2 deletions

View File

@ -11,6 +11,12 @@
overrides:
# We increased the timeout since comparison results speed were slowed down due to resolving
# Object.entries correctly.
enterprise-amazon-linux2-arm64-all-feature-flags-fuzzers:
- task: aggregation_timeseries_fuzzer
exec_timeout: 150 # 2.5 hours
enterprise-macos:
- task: replica_sets_jscore_passthrough
exec_timeout: 150 # 2.5 hours

View File

@ -247,13 +247,13 @@ tasks:
vars:
<<: *jstestfuzz_config_vars
# We have seen some common scenarios where the generated pipelines take a while to run and can
# hit some timeouts. We'll split 80000 pipelines across 80 files, compared to 80000 pipelines
# hit some timeouts. We'll split 70000 pipelines across 70 files, compared to 80000 pipelines
# across 20 files in the other generational agg fuzzers. This approach can be considered if we
# see similar timeouts elsewhere. It is not well understood whether/how we could pass
# 'numPipelines' as an argument in the yaml here, but it works as part of the
# 'jstestfuzz_vars' argument string. If a future reader better understands this evergreen
# integration, please update this comment and/or move numPipelines to a yaml arg here.
num_files: 80
num_files: 70
num_tasks: 20
jstestfuzz_vars: --diffTestingMode timeseries --numPipelines=1000
npm_command: agg-fuzzer