Skip to content

fine tune how to split the test suite #64

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
gnzlbg opened this issue Aug 4, 2018 · 1 comment
Closed

fine tune how to split the test suite #64

gnzlbg opened this issue Aug 4, 2018 · 1 comment
Labels
CI-Travis Travis-CI

Comments

@gnzlbg
Copy link
Contributor

gnzlbg commented Aug 4, 2018

The test suite was split in #62 into three test groups:

RUSTFLAGS="${ORIGINAL_RUSTFLAGS} --cfg test_v16  --cfg test_v32" cargo_test ${1}
RUSTFLAGS="${ORIGINAL_RUSTFLAGS} --cfg test_v64  --cfg test_v128" cargo_test ${1}
RUSTFLAGS="${ORIGINAL_RUSTFLAGS} --cfg test_v256 --cfg test_v512" cargo_test ${1}

We should fine tune this, and see if a different split, for example:

RUSTFLAGS="${ORIGINAL_RUSTFLAGS} --cfg test_v16  --cfg test_v32 --cfg test_v64" cargo_test ${1}
RUSTFLAGS="${ORIGINAL_RUSTFLAGS} --cfg test_v128 --cfg test_v256" cargo_test ${1}
RUSTFLAGS="${ORIGINAL_RUSTFLAGS} --cfg test_v512" cargo_test ${1}

performs faster on travis.


The following things have already been tried:

So a split into three commands might be just what we need.

@gnzlbg
Copy link
Contributor Author

gnzlbg commented Sep 12, 2018

The split has been working properly as is.

@gnzlbg gnzlbg closed this as completed Sep 12, 2018
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
CI-Travis Travis-CI
Projects
None yet
Development

No branches or pull requests

1 participant