diff options
| author | Som Snytt <som.snytt@gmail.com> | 2013-04-24 11:30:00 -0700 |
|---|---|---|
| committer | Paul Phillips <paulp@improving.org> | 2013-04-30 08:18:22 -0700 |
| commit | 6227837f54e07a538f33358da9160c0bc5192525 (patch) | |
| tree | 418def78471b8cf47197ce2433f823054f8982d0 /build.number | |
| parent | 0c6bcc9cc24eeeb13f88ab91e858e5d246e0947d (diff) | |
| download | scala-6227837f54e07a538f33358da9160c0bc5192525.tar.gz scala-6227837f54e07a538f33358da9160c0bc5192525.tar.bz2 scala-6227837f54e07a538f33358da9160c0bc5192525.zip | |
SI-7409 Par-Test: A crash is not a DNC for neg tests
A compiler crash does not count as Does Not Compile for
purposes of a negative test. Changing the test kind from
"neg" to "dnc" is out of scope for this PR.
Even if the user asks to update the check file with the
crash result, we must prevent him from doing so. Any
further attempts to update the check file with a crash
will dispatch the Scala SWAT squad which will race to
his location and physically restrain the user. Only
Martin holds the code which will allow the squad to
stand down. So make sure his cell is on next time you
want to --update-check.
A neg test will stop trying to compile after the first
failed round, which is all that matters.
By popular request, a new test outcome is emitted when
the check file is updated. It is called "Updated". It
even has its own short status, the double-plus that is
reminiscent of diff output.
Diffstat (limited to 'build.number')
0 files changed, 0 insertions, 0 deletions