jasocrow
jasocrow
Thanks for trying this out. I'll work on reproducing these issues and getting fixes in soon.
Ok, I think both issues you ran into were related to gdb trying to process many SIGUSR1 signals. I've updated `gdb_server.sh` to ignore these signals and hopefully this will get...
@0vercl0k Awesome, thanks for trying it out and starting to change things up to your liking. Good catch on the README. I guess 4 GB started working at some point...
@0vercl0k I can take a look at adding a symbolizer, but it might be a while before I can get to it.
Everything looks good to me, happy if you're ready to merge. Thanks!!
Oh, I just noticed one small thing, looks like the link to Kyle's site in linux_mode/README.md is not showing correctly.
Another issue I encountered after adding the `test-check` health check is that the bot fails with this error: ``` Aug 16 00:12:33 clusterfuzz-linux-pre-smt0 bash[12608]: mount: /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases-disk: mount point does not...
The default deploy also does not set up firewall rules to allow health checks to pass.
There's no Kubernetes job for processing code coverage info.
No Kubernetes job for retry stuck tasks.