-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-deterministic License Manager Error 4402 with latest release of MATLAB with windows-latest or macos-latest #43
Comments
Another job in which I am experiencing this is https://github.com/robotology/idyntree/blob/master/.github/workflows/matlab.yml .
|
Hi @traversaro, Thanks for the report. We are looking into it. Best, |
Thanks for the feedback @mcafaro ! |
Probably related PR: osqp/osqp-matlab#51 . |
* Do not run MATLAB tests on matlab latest version Workaround for matlab-actions/run-command#43
Workaround for matlab-actions/run-command#43 Workaround for robotology/robotology-superbuild#1492
also saw this error on windows-2019 with MATLAB latest |
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. |
It should be resolved on both v1 and v2. |
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. |
Workaround for matlab-actions/run-command#43 Workaround for robotology/robotology-superbuild#1492
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: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:
Downstream issue: robotology/robotology-superbuild#1492 .
The text was updated successfully, but these errors were encountered: