You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MPI test failures on the Windows build node left MATLAB processes (MPI worker nodes) running on the machine.
This prevented all subsequent jobs executed against that MATLAB release from starting with a series of Jenkins IO exceptions Unable to delete <job directory and subfolders>.
Build logs from the failing and subsequent aborted PR build are attached to this ticked.
Ed: this is NOT limited to runs with failing/timed out tests; an example has been seen where ALL tests passed and the build succeeded in all aspects except the post-build cleanup.
Output:
identification of method by which orphaned processes are created
method to cleanup orphaned MATLAB processes on test failure
The text was updated successfully, but these errors were encountered:
Orphaned R2019/smpd process locked _test/test_mpi_wrappers after run with all tests passing. <jenkins-url>/jenkins/job/PACE-neutrons/job/Herbert/job/Windows-10-2019b/62/
nickbattam-tessella
changed the title
Test failure(s) result in unusable build node
Unusable Windows build resulting from orphaned processes
Jul 8, 2020
nickbattam-tessella
changed the title
Unusable Windows build resulting from orphaned processes
Orphaned processes cause unusable Windows build node
Jul 8, 2020
MPI test failures on the Windows build node left MATLAB processes (MPI worker nodes) running on the machine.
This prevented all subsequent jobs executed against that MATLAB release from starting with a series of Jenkins IO exceptions
Unable to delete <job directory and subfolders>
.Build logs from the failing and subsequent aborted PR build are attached to this ticked.
Ed: this is NOT limited to runs with failing/timed out tests; an example has been seen where ALL tests passed and the build succeeded in all aspects except the post-build cleanup.
Output:
The text was updated successfully, but these errors were encountered: