-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
None
The two functions "fetch artifacts from little-endian" and "fetch artifacts from big-endian" are very similar. Instead, we could create one function that takes a parameter to indicate whether we want "little-endian" or "big-endian". It could look like this:
"fetch artifacts from endian" :
- command: s3.get
params:
aws_key: ${aws_key}
aws_secret: ${aws_secret}
remote_file: wiredtiger/${endian_format}-endian/${revision}/artifacts/WT_TEST.tgz
bucket: build_external
local_file: WT_TEST-${endian_format}-endian.tgz
- command: archive.targz_extract
params:
path: "WT_TEST-${endian_format}-endian.tgz"
destination: "wiredtiger/build_posix/test/format"
And be called this way:
- func: "fetch artifacts from endian"
vars:
endian_format: little
Furthermore, a few tasks related to endianness make a call to the script verify_wt_datafiles.sh. We could create the following function:
"verify wt datafiles":
- command: shell.exec
params:
working_dir: "wiredtiger"
script: |
set -o errexit
set -o verbose
./test/evergreen/verify_wt_datafiles.sh 2>&1
And simply call the function where necessary.
- is duplicated by
-
WT-8506 Evergreen - Create a function to execute the verify_wt_datafiles script
-
- Closed
-