Should we treat BUG messages as fatal errors during fuzzing?
While wondering why #21966 (moved) wasn't caught during consdiff code fuzzing, I noticed that in the C implementation failing to apply a generated diff is not a reason to assert, but rather an LD_BUG log message is generated. Unapplying the 21966 fix and fuzzing promptly leads to the discovery of that bug. I think it might make sense to ensure any BUG message that gets triggered fails an assertion if we're currently fuzzing?
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information