Navidem

Results 62 comments of Navidem

edge-orchestration: initial integration

Please fix the failure.

[filecoin-ref-fvm] Initial integration

Thanks for the PR. Could you please provide more information on some important users of ref-fvm (and probably Lotus)?

infra: rust coverage option is now stable

/gcbrun trial_build.py wasmtime servo oak --sanitizer coverage --fuzzing-engine libfuzzer

infra: rust coverage option is now stable

Could you please look into trial build failure?

Update clang to clang-17

@DavidKorczynski does Fuzz Introspector plugin work with clang15?

compile_native_go_fuzzer: only search for fuzz function in .go files

@kmoe friendly ping :)

Clusterfzz should prevent creating too many new bugs at once

> Thanks! bug throttling is certainly something that makes sense. > > @Navidem this might be something we can tackle after the variant analysis grouping. Sure, will take a note...

Unique bugs deduplicated into the same issue

Thanks for brining this to our attention, > One thing we noticed was that the first ~10 stack frames are similar This is actually the reason for the two bugs...

Add vendors to Python projects.

The CI failure is irrelevant to the changes, it is running out of disk space.

Seg fault when building with --fsanitize=introspector

`c-ares` is failing with linker internal error, too. But not seg fault necessary: [log](https://oss-fuzz-build-logs.storage.googleapis.com/log-c9699daa-1de8-492e-8e6f-cd4c80038ad7.txt) ``` Step #7 - "compile-libfuzzer-introspector-x86_64": /bin/bash ./libtool --tag=CXX --mode=link clang++ -O1 -fno-omit-frame-pointer -gline-tables-only -DFUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION -flegacy-pass-manager -flto...