You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the cfail test runner works by parsing rustc's stderr, and scanning the output for errors/warnings. It uses the pattern <filename>:<line>:<col> [error|warning] to check whether a line of output is an unexpected error.
This never succeeds on windows, because absolute paths start with a drive letter + colon, eg. "C:", and the colon breaks the pattern.
The result is that any number of additional errors are allowed to be generated without causing the cfail tests to fail.
The text was updated successfully, but these errors were encountered:
Currently the cfail test runner works by parsing rustc's stderr, and scanning the output for errors/warnings. It uses the pattern
<filename>:<line>:<col> [error|warning]
to check whether a line of output is an unexpected error.This never succeeds on windows, because absolute paths start with a drive letter + colon, eg. "C:", and the colon breaks the pattern.
The result is that any number of additional errors are allowed to be generated without causing the cfail tests to fail.
The text was updated successfully, but these errors were encountered: