Non-deterministic License Manager Error 4402 with latest release of MATLAB with windows-latest or macos-latest

[traversaro]

I have a GitHub Action job that frequently (around 4 times out of 5) on with release: latest on a step that uses matlab-actions/run-command@v1 with error:

  ======BEGIN LICENSE MANAGER ERROR======
  License checkout failed.
  License Manager Error 4402
  Missing root element in response
  
  Troubleshoot this issue by visiting: 
  https://www.mathworks.com/support/lme/4402
  
  Diagnostic Information:
  Feature: MATLAB_Distrib_Comp_Engine 
  License path:  
  Licensing error: 4402,0.
  ======END LICENSE MANAGER ERROR======
  
  exit status 1

other job that use R2022a or R2022b work fine all the time.

The job is https://github.com/robotology/robotology-superbuild/blob/master/.github/workflows/matlab-one-line-install-test.yml , recent job execution:

• recent job ended with a failure: https://github.com/robotology/robotology-superbuild/actions/runs/6346368869
• recent job ended with a a success: https://github.com/robotology/robotology-superbuild/actions/runs/6359421002

Downstream issue: robotology/robotology-superbuild#1492 .

[traversaro]

Another job in which I am experiencing this is https://github.com/robotology/idyntree/blob/master/.github/workflows/matlab.yml .

• recent job ended with a failure: https://github.com/robotology/idyntree/actions/runs/6367311894 (in this case, the failure is only on Windows)
• recent job ended with a a success: https://github.com/robotology/idyntree/actions/runs/6320523089

[mcafaro]

Hi @traversaro,

Thanks for the report. We are looking into it.

Best,
Mark

[traversaro]

Thanks for the feedback @mcafaro !

[traversaro]

Probably related PR: osqp/osqp-matlab#51 .

[fangq]

also saw this error on windows-2019 with MATLAB latest
https://github.com/fangq/jsonlab/actions/runs/6669729937/job/18128129445

[mcafaro]

This issue should hopefully be resolved. Can you please give it a try and report back?

[traversaro]

This issue should hopefully be resolved. Can you please give it a try and report back?

Thanks, I opened robotology/robotology-superbuild#1593 to check this . It is supposed to be solved in general or just for v2? No problem in updating to v2, just to understand.

[mcafaro]

It should be resolved on both v1 and v2.

[traversaro]

Everything seems to be working fine, thanks a lot! Let's close the issue, if anyone experience something similar feel free to re-open or open a new issue.