Skip to content

Some run-make-fulldeps don't fail if -include fails #83773

Closed
@jyn514

Description

@jyn514

I tried this code:

renamed:    run-make-fulldeps/exit-code/Makefile -> run-make/exit-code/Makefile
renamed:    run-make-fulldeps/exit-code/compile-error.rs -> run-make/exit-code/compile-error.rs
renamed:    run-make-fulldeps/exit-code/lint-failure.rs -> run-make/exit-code/lint-failure.rs
renamed:    run-make-fulldeps/exit-code/success.rs -> run-make/exit-code/success.rs

I expected to see this happen: The test fails, because the Makefile includes ../tools.mk which doesn't exist - it should include ../../run-make-fulldeps/tools.mk instead.

Instead, this happened: The test passes.

I can change it to a hard error by changing -include to include, but it seems bad to have a test that passes even if the commands it's running don't exist 😟

Meta

This is based off of a5029ac.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-testsuiteArea: The testsuite used to check the correctness of rustcC-bugCategory: This is a bug.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