[
https://issues.apache.org/jira/browse/MESOS-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095784#comment-15095784
]
Bernd Mathiske commented on MESOS-4075:
---------------------------------------
I thought solving this would make your life as release master easier, but so
would fixing any remaining crashes, which need to be worked on anyhow if they
occur. See above. I just changed the target version for this ticket to
indeterminate.
Long-term, I suggest we should solve it, even if tests run more slowly then and
you can only use this feature optionally. Getting a full assessment of what
does and does not work in one swoop expedites testing. Repeatedly rerunning the
tests with an incrementally updated list of test exclusions starts getting
inefficient once there is more than one crash involved. (This cost us a lot of
time in 0.26.0.) On second thought, maybe the latter procedure could be
automated as a band-aid?
> Continue test suite execution across crashing tests.
> ----------------------------------------------------
>
> Key: MESOS-4075
> URL: https://issues.apache.org/jira/browse/MESOS-4075
> Project: Mesos
> Issue Type: Improvement
> Components: test
> Affects Versions: 0.26.0
> Reporter: Bernd Mathiske
> Labels: mesosphere
>
> Currently, mesos-tests.sh exits when a test crashes. This is inconvenient
> when trying to find out all tests that fail.
> mesos-tests.sh should rate a test that crashes as failed and continue the
> same way as if the test merely returned with a failure result and exited
> properly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
