MATLAB Answers

Worker can't find attached files

122 views (last 30 days)
Hi Matlab Community,
We've set up a Jenkins server for our simulation code. We have a set of test cases, where output data of our code is compared to reference values from the literature or stable versions of the code. Matlab on jenkins server is Version 2020b/Linux.
One test case, which is going into a parfor loop, can't seem to find the source code files for the workers. Other test cases, which run basically the same parts of the code including this exact parfor loop, have no problems whatsoever. I get the following error:
Error using Driver_VLEmix (line 167)
The source code
(*********************************************/Driver_VLEmix.m) for
the parfor-loop that is trying to execute on the worker could not be found.
Auto attached files are being stored in the home directory of the Jenkins user. The file is on the other hand listed via listAutoAttachedFiles(gcp())
Files automatically added to the parallel pool:
*********************************************/Driver_VLEmix.m
I tried a run, where I manually attach the file, still the same result.
This error only occurs on the jenkins server. On our local machines, it works just fine (Linux 2019b, Win 2020b).
This is the only case, where I get the following message when the parpool is initialized:
Analyzing and transferring files to the workers ...done.
Which I'd guess is where the files are automatically attached. Any ideas what could be wrong?
Best regards,
Dominik
  3 Comments
PeymanS
PeymanS on 17 Mar 2021
Hi Dominik,
I have faced the same problem. Have you found the solution?
Best,
Peyman

Sign in to comment.

Accepted Answer

Dominik Schäfer
Dominik Schäfer on 17 Mar 2021
Hi Peyman,
one of the subfunctions in the parfor loop called the (not recommended) nansum function.
When we changed nansum to sum(A,'omitnan') everything worked as intended.
Hope this helps!
Best regards,
Dominik

More Answers (1)

Chien-Han Su
Chien-Han Su on 1 Jul 2021
Edited: Chien-Han Su on 1 Jul 2021
I accidentally triggered this error as well, and the fail is resulted from, in the parfor loop, an wrongly called non-existent variable/function due to typos.
I think for any one who has the same problem, one possible way to deal this is turn off the parallel procedure at first (using "for" instead of "parfor"). In this way, matlab will return a more detailed error massage, and that's how I figure it out.

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by