Workflows crash with a segmentation violation after `matlab-actions/[email protected]` finishes and before `matlab-actions/[email protected]` starts

[zaikunzhang]

Recently, it has been happening from time to time (but not always) that my workflows crash with a segmentation violation right after matlab-actions/[email protected] finishes and before matlab-actions/[email protected] starts.

Here are two examples:

crash1.log workflow1

crash2.log workflow2

Since the crash happens randomly, I do not expect it will be trivial to debug. But it will still be great if you could have a look.

Thanks.

[mcafaro]

Can you give matlab-actions/setup-matlab@v2-beta a try? It may increase the time required to set up MATLAB (particularly with older releases) but it may also help address this crash.

Note: with setup-matlab v2, you need to explicitly specify the products required for your build with the products input like so:

- name: Install MATLAB
  uses: matlab-actions/setup-matlab@v2-beta
  with:
    release: latest
    products: |
      Simulink
      Deep_Learning_Toolbox

See the v2 README for more details.

[zaikunzhang]

Thank you @mcafaro . I will try it.

[zaikunzhang]

Hi @mcafaro ,

Recently, it has been happening from time to time (but not always) that my workflows crash with a segmentation violation right after matlab-actions/[email protected] finishes and before matlab-actions/[email protected] starts.

Here are two examples:

crash1.log workflow1

crash2.log workflow2

The problem comes back. It has been happening randomly that workflows crash with a segmentation violation right after matlab-actions/setup-matlab@v2-beta finishes and before matlab-actions/run-command starts. The syndrom is identical to what I reported before.

It would be nice if you could take a look. Thanks!

Best regards, Zaikun

[mcafaro]

Hi Zaikun,

Is this happening on all workflows where you use setup-matlab or just particular workflows? How frequently is the crash occurring?

Thanks, Mark

[zaikunzhang]

Hi Mark,

It seems to be happening randomly on all my MATLAB workflows. I have not identified a pattern yet. It happens about every 1 out of 10~20 times.

Thank you very much!

Best regards, Zaikun

[zaikunzhang]

This seems to be happening more and more frequently now. Am I the only one who observes this?

I run ver at the very beginning of my run-command. This crash happens before the version information is printed.

Thanks.

[davidbuzinski]

Hi @zaikunzhang,

We have changed the way we start MATLAB in the new v2 releases of our actions (is it different from how MATLAB started using setup-matlab@v2-beta as well). I haven't seen this yet on v2 so I am curious if you will still experience it after upgrading to v2 for all matlab-actions. If we leave this issue open for a little while, can you update us here if you continue to see it?

Thanks, David

[zaikunzhang]

Hi @davidbuzinski , sure, I will keep this in mind. If you don't receive my report in a month, then it will mean that the problem has been resolved by the new release.

[davidbuzinski]

Hi @zaikunzhang , have you still been seeing these errors sporadically? Is it okay if we close this issue?

Thanks, David

[zaikunzhang]

Hi @davidbuzinski David,

Many thanks for keeping this in mind.

I haven't observed this recently. It should be fine now.

Zaikun