I think this is fine.
We have a bunch of compiler_crashers which are non-deterministic because they
trigger undefined behavior at runtime, such as dangling pointers, stack
overflow, etc.
Disabling this is OK for now (it is still in compiler_crashers/ so it is
understood it is not yet fixed). I
As part of the move to reset the Clang/LLVM stable branches to their new
versions, I disabled the
compiler_crashers/28616-swift-parser-parseexprsequence-swift-diag-bool-bool.swift
test because it was consistently failing to crash when I ran the tests
locally. (It is expected to crash, so the te
