Tests hanging on CI
Friedrich W. H. Kossebau
kossebau at kde.org
Sun Jan 20 13:39:06 GMT 2019
Am Donnerstag, 17. Januar 2019, 10:43:56 CET schrieb Ben Cooksley:
> On Sun, Jan 13, 2019 at 9:27 PM Ben Cooksley <bcooksley at kde.org> wrote:
> > Hi KDevelop Devs,
> Hi folks,
> > Currently we have an issue where the KDevelop's test_cmakemanager test
> > doesn't cleanup after itself properly on the CI system. This leads to
> > it leaving behind a "cmake -E server" process, which due to how CTest
> > works means it will wait indefinitely.
> > This requires manual intervention to sort out.
> > Could someone please investigate and sort this out?
> > A log showing the issue can be found at
> > https://build.kde.org/job/KDevelop/job/kdevelop/job/kf5-qt5%20SUSEQt5.10/2
> > 6/consoleFull
The issues seems to be that the test crashes. Which should be fixed
independently. But in any case, this can happen as it does now, so IMHO we
should be prepared for that, and not have the whole build fail on that.
Any code in the test to shutdown the cmake server will not be effective if the
test itself crashes, right?
Is there no way to somehow log by the test execution environment what other
processes a test triggers and collect them as last resort, if the test itself
fails to do so? Or could any such processes be somehow explicitly registered
somewhere. so the test environment can gracefully pick up the parts on a
More information about the KDevelop-devel