rust/ci/build_and_test.bat

set "RUSTFLAGS=-D warnings"
set "RUSTFMT_CI=1"

:: Print version information
rustc -Vv || exit /b 1
cargo -V || exit /b 1

:: Build and test main crate
cargo build --locked || exit /b 1
cargo test || exit /b 1

:: Build and test other crates
cd config_proc_macro || exit /b 1
cargo build --locked || exit /b 1
cargo test || exit /b 1
ci: include config_proc_macro crate in ci (#5389) * config_proc_macro: fix failing doctests * ci: include config_proc_macro crate in ci * [review] working native windows ci * [fix] add --locked file for ci * [fix] quoting of cmd variables 2022-06-21 10:23:13 -05:00			`set "RUSTFLAGS=-D warnings"`
Allow `#[ignore]` tests to run in rustfmt's test suite There are some tests in the rustfmt test suite that are ignored by default. I believe these tests are ignored because they have caused issues with the the `rust-lang/rust` test suite. However, we recently experienced an issue (5395) that would have been avoided had these tests been running. With the introduction of the new `#[rustfmt_only_ci_test]` attribute macro we can run these tests when the `RUSTFMT_CI` environment variable is set, which will presumably only be set during rustfmts CI runs. When the environment variable is not set the `#[rustfmt_only_ci_test]` will be replaced with an `#[ignore]`. 2022-06-21 18:28:04 -05:00			`set "RUSTFMT_CI=1"`
ci: include config_proc_macro crate in ci (#5389) * config_proc_macro: fix failing doctests * ci: include config_proc_macro crate in ci * [review] working native windows ci * [fix] add --locked file for ci * [fix] quoting of cmd variables 2022-06-21 10:23:13 -05:00
			`:: Print version information`
			`rustc -Vv \|\| exit /b 1`
			`cargo -V \|\| exit /b 1`

			`:: Build and test main crate`
			`cargo build --locked \|\| exit /b 1`
			`cargo test \|\| exit /b 1`

			`:: Build and test other crates`
			`cd config_proc_macro \|\| exit /b 1`
			`cargo build --locked \|\| exit /b 1`
			`cargo test \|\| exit /b 1`