Struct bootstrap::toolstate::ToolStateCheck

pub struct ToolStateCheck;

Trait Implementations

impl Clone for ToolStateCheck

fn clone(&self) -> ToolStateCheck

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ToolStateCheck

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Hash for ToolStateCheck

fn hash<__H: Hasher>(&self, state: &mut __H)

Feeds this value into the given Hasher.

fn hash_slice<H>(data: &[Self], state: &mut H)where H: Hasher, Self: Sized,

Feeds a slice of this type into the given Hasher.

impl PartialEq<ToolStateCheck> for ToolStateCheck

fn eq(&self, other: &ToolStateCheck) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

This method tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Step for ToolStateCheck

fn run(self, builder: &Builder<'_>)

Checks tool state status.

This is intended to be used in the checktools.sh script. To use this, set save-toolstates in config.toml so that tool status will be saved to a JSON file. Then, run x.py test --no-fail-fast for all of the tools to populate the JSON file. After that is done, this command can be run to check for any status failures, and exits with an error if there are any.

This also handles publishing the results to the history directory of the toolstate repo https://github.com/rust-lang-nursery/rust-toolstate if the env var TOOLSTATE_PUBLISH is set. Note that there is a separate step of updating the latest.json file and creating GitHub issues and comments in src/ci/publish_toolstate.sh, which is only performed on master. (The shell/python code is intended to be migrated here eventually.)

The rules for failure are:

• If the PR modifies a tool, the status must be test-pass. NOTE: There is intent to change this, see https://github.com/rust-lang/rust/issues/65000.
• All “stable” tools must be test-pass on the stable or beta branches.
• During beta promotion week, a PR is not allowed to “regress” a stable tool. That is, the status is not allowed to get worse (test-pass to test-fail or build-fail).

type Output = ()

PathBuf when directories are created or to return a Compiler once it’s been assembled.

fn should_run(run: ShouldRun<'_>) -> ShouldRun<'_>

When bootstrap is passed a set of paths, this controls whether this rule will execute. However, it does not get called in a “default” context when we are not passed any paths; in that case, make_run is called directly.

fn make_run(run: RunConfig<'_>)

Builds up a “root” rule, either as a default rule or from a path passed to us.

const DEFAULT: bool = false

Whether this step is run by default as part of its respective phase. true here can still be overwritten by should_run calling default_condition.

const ONLY_HOSTS: bool = false

If true, then this rule should be skipped if –target was specified, but –host was not

impl Copy for ToolStateCheck

impl Eq for ToolStateCheck

impl StructuralEq for ToolStateCheck

impl StructuralPartialEq for ToolStateCheck

Layout

Note: Most layout information is completely unstable and may even differ between compilations. The only exception is types with certain repr(...) attributes. Please see the Rust Reference's “Type Layout” chapter for details on type layout guarantees.

Size: 0 bytes