-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update CI config #5893
Update CI config #5893
Conversation
taiki-e
commented
Jul 28, 2023
•
edited
Loading
edited
- Remove duplicate target from cross-test
- Remove needless --test-threads=1 as RUST_TEST_THREADS=1 already specifies it
- Remove --cfg tokio_no_ipv6 as setup-cross-toolchain-action supports it
- Automatically cancel all outdated workflows on PR (currently this is only set for ci.yml)
- Remove --cfg tokio_no_atomic_u64 as tests/builds with --target target-specs/i686-unknown-linux-gnu.json handles these cases
- Remove duplicate target from cross-test - Remove needless --test-threads=1 (already specified by RUST_TEST_THREADS=1) - Remove --cfg tokio_no_ipv6 as setup-cross-toolchain-action supports it
Currently, this is only set for ci.yml.
RUST_TEST_THREADS: 1 | ||
RUSTFLAGS: --cfg tokio_unstable -Dwarnings --cfg tokio_no_ipv6 --cfg tokio_no_tuning_tests ${{ matrix.rustflags }} | ||
RUSTFLAGS: --cfg tokio_unstable -Dwarnings --cfg tokio_no_tuning_tests ${{ matrix.rustflags }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just realized these RUST*
flags should be set before Swatinem/rust-cache@v2
:
- name: Set RUST env
run: |
echo RUST_TEST_THREADS=1 >> "$GITHUB_ENV"
echo 'RUSTFLAGS=--cfg tokio_unstable -Dwarnings --cfg tokio_no_tuning_tests ${{ matrix.rustflags }}' >> "$GITHUB_ENV"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Considering how Swatinem/rust-cache works, it may be best for some workflows that meet certain conditions, but since we don't change rustflags often and sometimes set different rustflags for each step, I think it is also fine as-is.
tests/builds with --target target-specs/i686-unknown-linux-gnu.json handles these cases.