Displaying 5 results from an estimated 5 matches for "jno73y".
2013 Jan 16
0
[LLVMdev] [PATCH] A "very verbose" mode for FileCheck
...issue for me -- it is
> mostly mechanical. So should I change tests to use %FileCheck?
Here's a third attempt.
The new behavior is as follows:
1. In case of errors we always dump output to a temporary file and print
Saving input file "<stdin>" to "/tmp/filecheck.txt-Jno73y"
2. If --dump-input-on-error option is passed, FileCheck will also dump
input to stderr.
3. If FILECHECK_DUMP_INPUT_ON_ERROR env var is set, lit will replace
"%FileCheck" with "FileCheck --dump-input-on-error".
I will fix all tests in LLVM and Clang if we decide this is...
2013 Jan 17
4
[LLVMdev] [PATCH] A "very verbose" mode for FileCheck
...n advance for driving this forward. I'm sorry that such a simple thing is so complicated.
> The new behavior is as follows:
>
> 1. In case of errors we always dump output to a temporary file and print
>
> Saving input file "<stdin>" to "/tmp/filecheck.txt-Jno73y"
This doesn't make sense to me. It's really common in a normal development scenario to do something, test and have stuff fail. It doesn't make sense to dump things into /tmp in this case.
> 2. If --dump-input-on-error option is passed, FileCheck will also dump
> input to...
2013 Jan 16
3
[LLVMdev] [PATCH] A "very verbose" mode for FileCheck
On Wed, Jan 16, 2013 at 9:24 PM, Chris Lattner <clattner at apple.com> wrote:
>
> On Jan 16, 2013, at 10:32 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote:
>
>> Hello,
>>
>> When someone breaks a FileCheck-based test on some buildbot, sometimes
>> it may not be obvious *why* did it fail. If the failure can not be
>> reproduced locally, it can
2013 Jan 17
0
[LLVMdev] [PATCH] A "very verbose" mode for FileCheck
...this forward. I'm sorry that such a simple thing is so complicated.
>
>> The new behavior is as follows:
>>
>> 1. In case of errors we always dump output to a temporary file and print
>>
>> Saving input file "<stdin>" to "/tmp/filecheck.txt-Jno73y"
>
> This doesn't make sense to me. It's really common in a normal development scenario to do something, test and have stuff fail. It doesn't make sense to dump things into /tmp in this case.
>
>> 2. If --dump-input-on-error option is passed, FileCheck will also du...
2013 Jan 16
3
[LLVMdev] [llvm-commits] [PATCH] A "very verbose" mode for FileCheck
...cleaned up automatically? I don't think this should happen
in the "default" mode of the tool.
Other than that, the idea sounds awesome, and I'd be happy to see any
variation of it on the bots ASAP.
>
> Saving input file "<stdin>" to "/tmp/filecheck.txt-Jno73y"
>
> 2. If --dump-input-on-error option is passed, FileCheck will also dump
> input to stderr.
>
> 3. If FILECHECK_DUMP_INPUT_ON_ERROR env var is set, lit will replace
> "%FileCheck" with "FileCheck --dump-input-on-error".
>
> I will fix all tests in...