search for: timeouttest

...eout.test`` are taking much longer to run. I'm still not quite sure what happened in r270942 because the changes look benign but something definitely is going wrong. I'm currently looking at ``fuzzer-timeout.test`` at the following command is behaving very suspiciously ``` not LLVMFuzzer-TimeoutTest -timeout=1 %S/hi.txt 2>&1 | FileCheck %s --check-prefix=SingleInputTimeoutTest ``` When I run ``LLVMFuzzer-TimeoutTest -timeout=1 /path/to/hi.txt`` ASan is firing with same stack trace over and over again (piping the output to file a results in a file that is 259 MiB). I've attached the...

...> > I'm still not quite sure what happened in r270942 because the changes > look benign but something definitely is going wrong. > > I'm currently looking at ``fuzzer-timeout.test`` at the following > command is behaving very suspiciously > > ``` > not LLVMFuzzer-TimeoutTest -timeout=1 %S/hi.txt 2>&1 | FileCheck %s > --check-prefix=SingleInputTimeoutTest > ``` > > When I run ``LLVMFuzzer-TimeoutTest -timeout=1 /path/to/hi.txt`` ASan > is firing with same stack trace over and over again (piping the output > to file a results in a file that is 25...

...quite sure what happened in r270942 because the changes >> look benign but something definitely is going wrong. >> >> I'm currently looking at ``fuzzer-timeout.test`` at the following >> command is behaving very suspiciously >> >> ``` >> not LLVMFuzzer-TimeoutTest -timeout=1 %S/hi.txt 2>&1 | FileCheck %s >> --check-prefix=SingleInputTimeoutTest >> ``` >> >> When I run ``LLVMFuzzer-TimeoutTest -timeout=1 /path/to/hi.txt`` ASan >> is firing with same stack trace over and over again (piping the output >> to file a resu...