| commit | 9cf3782449646ec45228bbcdbd12466c4014d2aa | |
| author | Alexander Köplinger <alex.koeplinger@outlook.com> | |
| Wed, 21 Nov 2018 01:17:23 +0000 (21 02:17 +0100) | ||
| committer | GitHub <noreply@github.com> | |
| Wed, 21 Nov 2018 01:17:23 +0000 (21 02:17 +0100) | ||
| tree | d719c7de1e640c2f0e58a232791f04383021cf51 | treesnapshot (tar.gz zip) |
| parent | f63d97d384b1f418a38dd6684dbbb798b62a8b80 | commitdiff |
[tests] Propagate runtime exit code in test_op_il_seq_point.sh (#11749)
We weren't checking whether the runtime returned a zero exit code which
means if the compilation failed we still reported success.
Now the exit code is propagated all the way up and we report an error
both to make and to the xml result file.
Since iltests.exe contains a test with expected invalid IL this would
now cause a failure. The easiest fix is to just move that test from
mono/mini to mono/tests since all other tests are fine.
Fixes https://github.com/mono/mono/issues/11091
We weren't checking whether the runtime returned a zero exit code which
means if the compilation failed we still reported success.
Now the exit code is propagated all the way up and we report an error
both to make and to the xml result file.
Since iltests.exe contains a test with expected invalid IL this would
now cause a failure. The easiest fix is to just move that test from
mono/mini to mono/tests since all other tests are fine.
Fixes https://github.com/mono/mono/issues/11091