Xuanwo commented on issue #7808: URL: https://github.com/apache/opendal/issues/7808#issuecomment-4832661482
fuzz failed for timeout ``` [Environment] ASAN_OPTIONS=exitcode=77 -- | +----------------------------------------Release Build Stacktrace----------------------------------------+ | Command: /mnt/scratch0/clusterfuzz/resources/platform/linux/unshare -c -n /mnt/scratch0/clusterfuzz/bot/builds/clusterfuzz-builds_opendal_edb6e735381357c85f4985935b80afe7c8d3ef37/revisions/fuzz_reader_memory -rss_limit_mb=2560 -timeout=60 -runs=100 /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/timeout-8dc65d6ae43f08746d3a7c584411eb7c5e7c9366 | Time ran: 62.599844455718994 | | INFO: Running with entropic power schedule (0xFF, 100). | INFO: Seed: 550328805 | INFO: Loaded 1 modules (298857 inline 8-bit counters): 298857 [0x574ba2e729a0, 0x574ba2ebb909), | INFO: Loaded 1 PC tables (298857 PCs): 298857 [0x574ba2ebb910,0x574ba334afa0), | /mnt/scratch0/clusterfuzz/bot/builds/clusterfuzz-builds_opendal_edb6e735381357c85f4985935b80afe7c8d3ef37/revisions/fuzz_reader_memory: Running 1 inputs 100 time(s) each. | Running: /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/timeout-8dc65d6ae43f08746d3a7c584411eb7c5e7c9366 | ALARM: working on the last Unit for 61 seconds | and the timeout value is 60 (use -timeout=N to change) | ==248== ERROR: libFuzzer: timeout after 61 seconds | #0 0x574ba18133a1 in __sanitizer_print_stack_trace /rustc/llvm/src/llvm-project/compiler-rt/lib/asan/asan_stack.cpp:87:3 | #1 0x574ba28a8c58 in fuzzer::PrintStackTrace() /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:210:5 | #2 0x574ba288c71b in fuzzer::Fuzzer::AlarmCallback() /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:304:5 | #3 0x7d478d3bd41f in libpthread.so.0 ``` Need to firgure what happened. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
