Hi,
I am reaching out to you wearing the hat of the apache log4net community.
I'll give you some context first.
We are in the process of automating the builds and tests for our various
targeted frameworks. We still struggle with gettibg the netstandard-1.3
tests to work. Some time ago I already had a conversation with Rob Prouse
about this. I was able to find a good combination of arguments to get the
test results logged into a trx fike that can be consumed by jenkins. The
tests are run on a ubuntu machine that starts up a docker container based
on microsoft/dotnet:1.1-sdk.
What we observe is that the test suite is run and when a test fails, the
tedt process does not terminate and hangs there until jenkins kills the
pipeline after the 4 hour timeout. The last lifesign is this message:
[exec] The active test run was aborted. Reason: Unable to
communicate with test host process.
Sending interrupt signal to process
Cancelling nested steps due to timeout
After 10s process did not stop
Unfortunately we are unable to reproduce the issue when running the test
locally and we have yet found no way to find out what actually goes wrong
or what we could do to avoid the issue. Would you please help us
troubleshoot and find a solution to this situation?
The source can be found here:
https://github.com/apache/logging-log4net/tree/feature/cd-pipeline
The pipeline configuration is in the Jenkinsfile. The test is run via nant.
So the build target can be found at the very end of this file:
https://github.com/apache/logging-log4net/blob/feature/cd-pipeline/tests/nant.build
And last but not least, the full jenkins build console output can be found
here:
https://builds.apache.org/job/logging-log4net/job/feature%252Fcd-pipeline/192/console
Best regards,
Dominik
