It looks like some tool testsuites (like clippy's or rustfmt's) will ignore the no fail fast option. For example running ./x.py test --no-fail-fast clippy will stop after compile-test fails, something common in big endian platforms.
If I understand correctly this seems to be because bootstrap is not passing --no-fail-fast to cargo test in every tool implementation. Currently, the flag is passed in the Step trait implementation of some tools (i.e. cargo), right after calling tool::prepare_tool_cargo(). But others like mentioned clippy or rustfmt are missing it.
It looks like some tool testsuites (like
clippy's orrustfmt's) will ignore the no fail fast option. For example running./x.py test --no-fail-fast clippywill stop after compile-test fails, something common in big endian platforms.If I understand correctly this seems to be because bootstrap is not passing
--no-fail-fasttocargo testin every tool implementation. Currently, the flag is passed in theSteptrait implementation of some tools (i.e. cargo), right after callingtool::prepare_tool_cargo(). But others like mentioned clippy or rustfmt are missing it.