Skip to content

docs: Known issues: path to itself #86

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stanislaw merged 1 commit into from
Dec 29, 2019
Merged

docs: Known issues: path to itself #86

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions docs/05-check-commands.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,6 @@ For all of the examples below, please note:

- ``.check`` extension is chosen arbitrarily. FileCheck can work with any file
names.
- FileCheck always prints its own path to the output. This always happens
regardless of input.
- When ``echo`` is used with the ``-e`` flag, the ``\n`` symbols are
treated as newline symbols. We use it to simulate multiline input for
FileCheck.
Expand Down
8 changes: 8 additions & 0 deletions docs/08-known-issues.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,14 @@
Known issues
============

FileCheck always prints a full path to itself
---------------------------------------------

LLVM FileCheck always prints its own path to the output so the first line is
always the path. This always happens regardless of a test outcome: success or
failure. FileCheck.py follows LLVM FileCheck and does the same, even though
there seems to be no reason to do that every time.

Unintuitive behavior of CHECK-NOT
---------------------------------

Expand Down