Skip to content

More systematic compile/run markup for "pass" UI tests #61712

@petrochenkov

Description

@petrochenkov

TLDR:

In test files: // check-pass // build-pass // run-pass In `x.py` command line (forcing): --force =check --force >=check --force <=check --force =build --force >=build --force <=build --force =run --force >=run --force <=run In `x.py` command line (running a subset): --select =check --select >=check --select <=check --select =build --select >=build --select <=build --select =run --select >=run --select <=run 

TODO:
More detailed description, motivation, etc.

cc @Centril

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-testsuiteArea: The testsuite used to check the correctness of rustcC-enhancementCategory: An issue proposing an enhancement or a PR with one.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions