Currently all 3 cppsuite search near tests run under a single task for both the default and stressful configurations. This is problematic as each one will overwrite the previous runs WT_TEST directory as such at the end of the test only the 3rd search near test's data files will remain.
Additionally the log levels used in the tests are quite spammy and should be adjusted to be TRACE level instead of INFO. An example log can be found here: log
Their evergreen.yml entries are shown below:
- name: cppsuite-search-near-default
tags: ["pull_request"]
depends_on:
- name: compile
commands:
- func: "fetch artifacts"
- command: shell.exec
params:
working_dir: "wiredtiger/build_posix/"
script: |
set -o errexit
set -o verbose
${test_env_vars|} $(pwd)/test/cppsuite/run -t search_near_01 -f test/cppsuite/configs/search_near_01_default.txt -l 2
${test_env_vars|} $(pwd)/test/cppsuite/run -t search_near_02 -f test/cppsuite/configs/search_near_02_default.txt -l 2
${test_env_vars|} $(pwd)/test/cppsuite/run -t search_near_03 -f test/cppsuite/configs/search_near_03_default.txt -l 2
- name: cppsuite-search-near-stress
depends_on:
- name: compile
commands:
- func: "fetch artifacts"
- command: shell.exec
params:
working_dir: "wiredtiger/build_posix/"
script: |
set -o errexit
set -o verbose
${test_env_vars|} $(pwd)/test/cppsuite/run -t search_near_01 -f test/cppsuite/configs/search_near_01_stress.txt -l 2
${test_env_vars|} $(pwd)/test/cppsuite/run -t search_near_02 -f test/cppsuite/configs/search_near_02_stress.txt -l 2
${test_env_vars|} $(pwd)/test/cppsuite/run -t search_near_03 -f test/cppsuite/configs/search_near_03_stress.txt -l 2
Scope:
- Split the 2 search near tasks into 6 search near tasks.
- Reduce amount of messages logged to INFO so logs are no longer spammy.
- related to
-
WT-8665 Reduce the amount of logs generated by search_near_03
-
- Closed
-