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
i have several Unittests and at least one of them checks if everything works properly using the parallel toolbox. The test is not failing after all, but Jenkins returns "ERROR: MATLAB error Exit Status: 0x00000001". The reports itself tell me that the test went sucessfull, so it must happen somehow after the test. I could also narrow down the problem to this one test, because i started to deactivate all other tests until only the ones with the parallel toolbox were left.
I assume that Jenkins just kills the process, because the window of the simulation manager closes on it's own, maybe this has to do with the problem. Do you have an idea how to solve this problem? I'm shutting down the pool within the script, so i'm not sure what exactly the problem is.
Thanks!
Adrian
Starting parallel pool (parpool) using the 'local' profile ...
Preserving jobs with IDs: 1 2 3 4 5 6 7 because they contain crash dump files.
You can use 'delete(myCluster.Jobs)' to remove all jobs created with profile local. To create 'myCluster' use 'myCluster = parcluster('local')'.
Connected to the parallel pool (number of workers: 6).
[26-Jan-2022 16:31:32] Checking for availability of parallel pool...
[26-Jan-2022 16:31:33] Starting Simulink on parallel workers...
[26-Jan-2022 16:31:40] Configuring simulation cache folder on parallel workers...
[26-Jan-2022 16:31:41] Loading model on parallel workers...
[26-Jan-2022 16:31:45] Running simulations...
[26-Jan-2022 16:31:47] Completed 1 of 1 simulation runs
[26-Jan-2022 16:31:47] Cleaning up parallel workers...
Unsupported file format for export.
Cleared PLECS module
Parallel pool using the 'local' profile is shutting down.
Done UnitTest_Debugging/RunModel_MultiCore in 55.8235 seconds
Tearing down UnitTest_Debugging
Done tearing down UnitTest_Debugging in 0 seconds
Done UnitTest_Debugging in 89.689 seconds
__________
ERROR: MATLAB error Exit Status: 0x00000001
Build step 'Run MATLAB Tests' changed build result to FAILURE
Finished: FAILURE
The text was updated successfully, but these errors were encountered:
Okay, the error happens when the Simulation Manager window opens during the unit test, passing to the parsim "'ShowSimulationManager', 'off'" solves the problem.
Is this a problem that is known when doing unit tests that include GUI elements or is it a problem exclusively with the Simulation Manager?
Hello,
i have several Unittests and at least one of them checks if everything works properly using the parallel toolbox. The test is not failing after all, but Jenkins returns "ERROR: MATLAB error Exit Status: 0x00000001". The reports itself tell me that the test went sucessfull, so it must happen somehow after the test. I could also narrow down the problem to this one test, because i started to deactivate all other tests until only the ones with the parallel toolbox were left.
I assume that Jenkins just kills the process, because the window of the simulation manager closes on it's own, maybe this has to do with the problem. Do you have an idea how to solve this problem? I'm shutting down the pool within the script, so i'm not sure what exactly the problem is.
Thanks!
Adrian
The text was updated successfully, but these errors were encountered: