matlab-actions / setup-matlab

Set up your GitHub Actions workflow with a specific version of MATLAB.
BSD 3-Clause "New" or "Revised" License
76 stars 10 forks source link

Planned support for Windows? #18

Closed LaurentRDC closed 8 months ago

LaurentRDC commented 3 years ago

Hello,

This repo is awesome! I'm using it to test MATLAB support for pandoc-plot, but at this time only Linux machines are supported. Any plans to support Windows for Github-hosted runners?

Thanks!

mcafaro commented 3 years ago

Hi Laurent,

Great to hear the MATLAB actions are working well for you! Yes, we would like to support Windows as soon as we can figure out an effective delivery method to get MATLAB on Windows GitHub-hosted runners. We're working on it now.

Best, Mark

PMeira commented 3 years ago

@mcafaro Happy to know Windows support is planned! Just found out about MATLAB Actions and it will save me a lot of time in the future.

If you allow me an uninformed suggestion, maybe packaging MATLAB as a VHD/VHDX and mounting that to a folder could work.

andreped commented 2 years ago

Any update on the Windows support, @mcafaro ? Would be a great feature, and desperately needed for a project I am involved in.

mcafaro commented 2 years ago

@andreped Nothing to share yet. In the meantime, are you aware of GitHub self-hosted runners? That could be a decent stopgap if you need to test against Windows ASAP.

andreped commented 2 years ago

@andreped Nothing to share yet. In the meantime, are you aware of GitHub self-hosted runners? That could be a decent stopgap if you need to test against Windows ASAP.

Hmm, interesting, @mcafaro. Will probably look into this to have some temporary support for Windows for my application.

Perhaps my use-case it ouside the scope of this issue, but what I want to do might not be supported either. What I want to do is to be able to build a standalone application of some software my team is developing. We wish to support the three different operating systems: Windows, macOSX, and Ubuntu Linux.

I am able to do this for both C++ and Python programs, without any issues, I have actually built softwares and made installers for both before using GitHub Actions. However, I am not sure whether this is possible to do using GitHub Actions with MATLAB, as of now.

Do you have any thoughts regarding what is required on your end to make this possible? Or perhaps, maybe this is already possible to do for Ubuntu Linux/macOSX and I am just being silly? Anyways, I am currently attempting to set this up, so any information regarding this issue would be much appreciated! :] In advance, thanks!

mcafaro commented 2 years ago

@andreped When you say a "standalone application", are you talking about a standalone application built via MATLAB Compiler (i.e. an application that does not require the target machine to have MATLAB installed in order to run)?

andreped commented 2 years ago

@andreped When you say a "standalone application", are you talking about a standalone application built via MATLAB Compiler (i.e. an application that does not require the target machine to have MATLAB installed in order to run)?

Yes.

mcafaro commented 2 years ago

@andreped The setup-matlab action does not currently license MATLAB Compiler, so even with Windows support you will not be able to produce a standalone application without using a self-hosted runner.

andreped commented 2 years ago

@mcafaro I see... I was hoping that it was possible, or at least in the near future, to be able to use our own MATLAB license when doing CI with GitHub Actions. That should be possible, as licenses can be stored encrypted using GitHub Secrets.

However, perhaps there are other challenges regarding using licensed MATLAB versions on the cloud, that I am not aware of. Same for building standalone applications. Any thoughts on that? And are you planning to make support for such a workflow in the near future? I guess this requires that it is possible to use the MATLAB Compiler on the cloud, which requires a MATLAB license, right?

mcafaro commented 2 years ago

@andreped MATLAB licenses are typically tied to a machine, which makes it tricky to use them with ephemeral agents, like GitHub-hosted agents, without running a licensing server. We are working on a bring-your-own-license approach where you store a token linked to your license in a secret env variable, but I do not have a timeline to share on that.

At the moment, setup-matlab automatically licenses MATLAB, Simulink, and most add-on products for public projects. The exceptions include coder and compiler products like MATLAB Compiler.

mcafaro commented 2 years ago

Hi folks,

matlab-actions/setup-matlab@v1.1.0 contains limited, undocumented, support for Windows and macOS GitHub-hosted runners. On these platforms, only MATLAB and Simulink are installed (no toolboxes) and only releases R2021a and above are available.

We hope to provide greater support for Windows and macOS in the future but this early access should be particularly useful for folks that need to compile MEX files across all platforms.

Best regards, Mark

P.S. There is a known issue on Windows where MATLAB will print a "thread_monitor::launch: _beginthreadex failed" message while exiting. It should not affect the results of your run.

bcoconni commented 2 years ago

Great ! Is the mex compiler currently available as well for Windows and MacOS X ?

mcafaro commented 2 years ago

Great ! Is the mex compiler currently available as well for Windows and MacOS X ?

Yes it is.

bcoconni commented 2 years ago

@mcafaro

On these platforms, only MATLAB and Simulink are installed (no toolboxes) and only releases R2021a and above are available.

Actually regarding MacOSX, R2020a and above are supported (I discovered that after inserting a typo in the release name 2020b instead of R2020b)

An error occurred during installation: available releases for maci64: [R2021b R2021a R2020b R2020a]
bcoconni commented 2 years ago

The header file mclcppclass.h seems to be missing on the MacOSX installation, whatever the MATLAB version used.

bcoconni commented 2 years ago

And the header file mclcppclass.h seems to be also missing on the Windows installation. Would it be possible to include this header file in matlab-actions/setup-matlab@v1.1.0 for both MacOSX and Windows ?

Thanks.

mcafaro commented 2 years ago

@bcoconni Yes that is true. macOS goes back to R2020a. Windows goes back to R2021a. Thanks for clarifying.

mclcppclass.h is part of MATLAB Compiler. Only MATLAB and Simulink are installed on these platforms at the moment. No toolboxes.

How are you making use of mclcppclass.h? I can discuss it with the team.

bcoconni commented 2 years ago

mclcppclass.h is part of MATLAB Compiler. Only MATLAB and Simulink are installed on these platforms at the moment. No toolboxes.

Well, since we are not using the MATLAB Compiler your statement made me think that we might not need to include mclmppclass.h actually and, after removing #include "mclmppclass.h", our S-Function now compiles on MacOSX and Windows ! :+1: :tada:

Thanks for the tip @mcafaro :smile:

How are you making use of mclcppclass.h? I can discuss it with the team.

The problem was that as I am not the author of the C++ file that included mclmppclass.h, I was struggling ~a lot~ a bit !

mfry-ll commented 2 years ago

@mcafaro this is great, thank you!

Is the intent to include MATLAB toolboxes in the future? I have a number of tests that depend on the Control System Toolbox and having that toolbox accessible would be very helpful.

mcafaro commented 2 years ago

@mfry-ll yes but it likely won't be until v2.

We have not come up with a system that can deliver MATLAB + all toolboxes to Windows and macOS as efficiently as we can to Linux. So in v2, we may have folks explicitly specify the toolboxes they want available on setup-matlab. How would you feel about that?

H0R5E commented 2 years ago

@mcafaro, we'd be very happy with that solution.

mfry-ll commented 2 years ago

@mcafaro Yes, that would work great

imciner2 commented 2 years ago

Is there any progress on adding toolboxes to the Windows and macOS runners? I have a package I am working on where I need the half type, so it needs the Fixed point designer toolbox to run, which works on the Linux-based runners, but not Windows or macOS.

mcafaro commented 2 years ago

Hi @imciner2, there's a good amount of behind-the-scenes work to do before we can add toolboxes to Windows and macOS. I think we're still a few months out. It will almost certainly require a move from v1 to v2 setup-matlab.

gllmflndn commented 1 year ago

Thanks for all of this @mcafaro. I call mexext on Linux and macOS but it doesn't seem to be available from Windows. If that's indeed the case, could it be added?

mcafaro commented 1 year ago

@gllmflndn mexext should be available on Windows. I just ran a build to confirm and it worked. Can you show me a build with the issue?

gllmflndn commented 1 year ago

@mcafaro Thanks for the quick response and sorry for not being precise enough. I want to use mex and mexext from bash, outside of run-command. Compilation takes place through a Makefile so I call mex from outside MATLAB and I would also would like to be able to call mexext. The following works from Linux and macOS but not Windows:

      - name: Get MEX extension
        run: echo "MEXEXT=$(mexext)" >> $GITHUB_ENV
      - name: Upload Artifact
        uses: actions/upload-artifact@v3
        with:
          name: mex-${{matrix.os}}-${{matrix.version}}
          path: ./**/*.${{env.MEXEXT}}
          retention-days: 1
mcafaro commented 1 year ago

@gllmflndn Depending on the shell you're using for run, you may need to include the .bat extension to call mexext (and mex) on Windows.

      - name: Get MEX extension on Windows
        run: echo "MEXEXT=$(mexext.bat)" >> $GITHUB_ENV

I think bash will require the extension, where PowerShell and cmd will not.

gllmflndn commented 1 year ago

Thanks @mcafaro! Your tests in the mexext repo confirm that mexext is indeed available and can be called with mexext or mexext.bat from PowerShell in a run. From a PowerShell terminal on my local machine, echo "MEXEXT=$(mexext)" and echo "MEXEXT=$(mexext.bat)" both return MEXEXT=mexw64 as expected but not from run in GitHub Actions (that uses PowerShell by default). This is not an issue with setup-matlab so I will not hijack this thread further! EDIT: I was looking at the wrong place: the issue is with $GITHUB_ENV - on Windows, one needs to use $env:GITHUB_ENV instead.

davidbuzinski commented 1 year ago

Hi all,

matlab-actions/setup-matlab@v2-beta supports using toolboxes on Windows and Linux runners. In order to use this feature, it is required that you list the additional products needed for your build, as specified in the README. Coder and compiler products, like MATLAB Compiler, can be installed, but a license must be provided for these products.

Please note that this feature is in beta. We hope to provide Mac support and a consistent API in a stable v2 release of setup-matlab in the future.

Feel free to create issues if something comes up while trying out the v2-beta release.

Best, David

gllmflndn commented 1 year ago

Hi @davidbuzinski, thanks for sharing this. I would be interested in running the MATLAB Compiler on GitHub-hosted Runners:

Coder and compiler products, like MATLAB Compiler, can be installed, but a license must be provided for these products.

How does that work? I can see that there are now MATHWORKS_ACCOUNT and MATHWORKS_TOKEN environment variables.

davidbuzinski commented 1 year ago

Hi @gllmflndn,

Hi @davidbuzinski, thanks for sharing this. I would be interested in running the MATLAB Compiler on GitHub-hosted Runners:

I would suggest sending an email to continuous-integration@mathworks.com if you are interested in leveraging an existing license in order to use products like coders or compilers on Github-hosted runners or if there is a need to leverage this action on GitHub-hosted runners for private projects.

acampbel commented 1 year ago

Hi all,

matlab-actions/setup-matlab@v2-beta supports using toolboxes on Windows and Linux runners. In order to use this feature, it is required that you list the additional products needed for your build, as specified in the README. Coder and compiler products, like MATLAB Compiler, can be installed, but a license must be provided for these products.

Please note that this feature is in beta. We hope to provide Mac support and a consistent API in a stable v2 release of setup-matlab in the future.

Feel free to create issues if something comes up while trying out the v2-beta release.

Best, David

@mfry-ll @H0R5E @imciner2,

Have any of you been able to try the use of toolboxes, like Control System Toolbox or Fixed-Point Designer in your Windows and Linux builds using v2-beta? Interested in any of your experiences or feedback.

H0R5E commented 1 year ago

@acampbel, I am just reconfiguring our CI to use the beta now on a feature branch here. My only feeback so far is that it would be more natural to specify the products as a yaml list rather than using a space delimited list. So,

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

instead of:

- name: Install MATLAB
  uses: matlab-actions/setup-matlab@v2-beta
  with:
    release: latest
    products: Simulink Simscape Simscape_Multibody
H0R5E commented 1 year ago

OK, I just checked the test logs and I have a number of different failures (noting that all these tests work on Linux runners).

For R2020b:

The tests wig out straight away:

D:\a\_actions\matlab-actions\run-command\v1\dist\bin\win64\run-matlab-command.exe cd('C:\Users\RUNNER~1\AppData\Local\Temp\run_matlab_command-7tzm7S');command_89b8[12](https://github.com/H0R5E/WEC-Sim/actions/runs/3892926025/jobs/6644918365#step:6:15)a8_e476_48a8_9eb8_5644dad63031
  exit status 0xc0000005
Error: Error: The process 'D:\a\_actions\matlab-actions\run-command\v1\dist\bin\win64\run-matlab-command.exe' failed with exit code 1

For 2021a and 2021b:

Simscape seems to fail with a segfault (2021a 2021b):

--------------------------------------------------------------------------------
               Access violation detected at 2023-01-11 13:06:29 +0000
  --------------------------------------------------------------------------------

  Configuration:
    Crash Decoding           : Disabled - No sandbox or build area path
    Crash Mode               : continue (default)
    Default Encoding         : windows-[125](https://github.com/H0R5E/WEC-Sim/actions/runs/3892926025/jobs/6644918577#step:6:127)2
    Deployed                 : false
    Graphics Driver          : Unknown software 
    Graphics card 1          : Microsoft ( 0x0 ) Microsoft Hyper-V Video Version 10.0.20348.1 (2006-6-21)
    Java Version             : Java 1.8.0_202-b08 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
    MATLAB Architecture      : win64
    MATLAB Entitlement ID    : Unknown
    MATLAB Root              : C:\hostedtoolcache\windows\MATLAB\9.10.0\x64
    MATLAB Version           : 9.10.0.2015706 (R2021a) Update 7
    OpenGL                   : software
    Operating System         : Microsoft Windows Server 2022 Datacenter
    Process ID               : 784
    Processor ID             : x86 Family 6 Model 85 Stepping 4, GenuineIntel
    Session Key              : e673e348-39d9-48df-a90c-2d1f9d97104a
    Window System            : Version 10.0 (Build 20348)

  Fault Count: 1

  Abnormal termination:
  Access violation

  Current Thread: 'MCR 0 interpreter thread' id 5756

  Register State (from fault):
    RAX = 0000000000000000  RBX = 000001dc2c461f70
    RCX = 000001dc38567250  RDX = 00000042c09d2780
    RSP = 00000042c09d2600  RBP = 00000042c09d2700
    RSI = 00000042c09d2828  RDI = 000001dc38567250

     R8 = 000001dc38567250   R9 = 0000000000000001
    R10 = 0000000000000003  R11 = 00000042c09d2770
    R12 = 00000042c09d34c8  R13 = 0000000000000000
    R14 = 00000042c09d2780  R15 = 00000042c09d32a0

    RIP = 00007ff8b1979bdf  EFL = 00010246

     CS = 0033   FS = 0053   GS = 002b

For latest:

Dies eventually in a similar fashion to 2021a and 2021b, but getting something extra, which I think is related to a progress bar:

================================================================================
  Error occurred while setting up or tearing down bemioTest.
  As a result, all bemioTest tests failed and did not run to completion.
      ---------
      Error ID:
      ---------
      'MATLAB:services:MissingRequiredCapability'
      --------------
      Error Details:
      --------------
      Error using matlab.internal.lang.capability.Capability.require
      Support for Java user interfaces is required, which is not available on this platform.

      Error in waitbar (line 46)
          Capability.require(Capability.Swing);

      Error in readWAMIT (line [37](https://github.com/H0R5E/WEC-Sim/actions/runs/3892926025/jobs/6644919376#step:6:39))
      p = waitbar(0,'Reading WAMIT output file...');  % Progress bar

      Error in bemioTest/testReadWAMIT (line 51)
                  hydro = readWAMIT(hydro,'sphere.out',[]);
  ================================================================================

I wonder if the segfault is related to the parallel toolbox? I note that it's being installed by default. Is there a way to stop it being installed so I can check if that is the issue?

davidbuzinski commented 1 year ago

Hi @H0R5E, I agree that specifying products as a yaml list would be more natural, but unfortunately I don't believe list inputs are supported by Github Actions authored by third-parties. Alternatively, you can specify the list of products as a multiline string like this:

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

The crashes you are seeing during testing look interesting. It appears to be related to how we are running MATLAB in CI environments. We are not currently able to remove the Parallel Computing Toolbox requirement, but there is work being done to remove it in the future. I was able to reproduce the segfault you are seeing and will reach out to some folks internally to see if we can get this resolved.

H0R5E commented 1 year ago

@davidbuzinski, thanks for the feedback!

H0R5E commented 1 year ago

@davidbuzinski, has there been any progress with this? Many thanks.

davidbuzinski commented 1 year ago

@H0R5E, Yes, I found that the errors seen with waitbar when running with no display on Windows is a known issue. I was told that they should be fixed as of R2022b update 4. Can you try again with Windows latest to see if those errors are still present?

I have also found some matches for the stack frame from for the crash at the bottom and am still narrowing in on the cause. Can you confirm if you are using the physical modelling features from Simscape?

Thanks, David

imciner2 commented 1 year ago

Thanks for this! I just added Windows to my CI with the Fixed-Point Designer toolbox, and it works.

Two things I noted though.

  1. I get a warning when it just uses the latest release (doesn't seem related to the toolbox specification though)
    Run matlab-actions/setup-matlab@v2-beta
    with:
    products: Fixed-Point_Designer
    release: latest
    Setting up MATLAB
    "C:\Program Files\PowerShell\7\pwsh.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command "$ErrorActionPreference = 'Stop' ; try { Add-Type -AssemblyName System.IO.Compression.ZipFile } catch { } ; try { [System.IO.Compression.ZipFile]::ExtractToDirectory('D:\a\_temp\53078015-7b71-4c5c-8782-6c1d4a2a6877', 'D:\a\_temp\6978282d-4f7f-462f-84c9-f2b6b0643dad', $true) } catch { if (($_.Exception.GetType().FullName -eq 'System.Management.Automation.MethodException') -or ($_.Exception.GetType().FullName -eq 'System.Management.Automation.RuntimeException') ){ Expand-Archive -LiteralPath 'D:\a\_temp\53078015-7b71-4c5c-8782-6c1d4a2a6877' -DestinationPath 'D:\a\_temp\6978282d-4f7f-462f-84c9-f2b6b0643dad' -Force } else { throw $_ } } ;"
    "C:\Program Files\Git\usr\bin\chmod.exe" +x D:\a\_temp\6978282d-4f7f-462f-84c9-f2b6b0643dad\bin\win64\mpm.exe
    D:\a\_temp\6978282d-4f7f-462f-84c9-f2b6b0643dad\bin\win64\mpm.exe install --release=r2022blatest --destination=C:\hostedtoolcache\windows\MATLAB\9.13.0\x64 --products Fixed-Point_Designer MATLAB Parallel_Computing_Toolbox
    Warning: Invalid syntax of update level, using latest update for R2022b.
  2. Capitalization of the toolboxes/products matter (I don't know if it is just me, but I first tried all lowercase instead since that was what came naturally to me).
H0R5E commented 1 year ago

@davidbuzinski, thank you, the waitbar error is now fixed on latest. We're using Simscape Multibody, so yes, I believe that would count as a physical modelling feature. I got a long stack trace in the logs from the last run, as follows:

--------------------------------------------------------------------------------
               Access violation detected at 2023-02-15 12:01:41 +0000
  --------------------------------------------------------------------------------

  Configuration:
    Crash Decoding           : Disabled - No sandbox or build area path
    Crash Mode               : continue (default)
    Default Encoding         : UTF-8
    Deployed                 : false
    Graphics Driver          : Uninitialized software 
    Graphics card 1          : Microsoft ( 0x0 ) Microsoft Hyper-V Video Version 10.0.20348.1 (2006-6-21)
    Java Version             : Java 1.8.0_202-b08 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
    MATLAB Architecture      : win64
    MATLAB Entitlement ID    : Unknown
    MATLAB Root              : C:\hostedtoolcache\windows\MATLAB\9.13.0\x64
    MATLAB Version           : 9.13.0.2166757 (R2022b) Update 4
    OpenGL                   : software
    Operating System         : Microsoft Windows Server 2022 Datacenter
    Process ID               : 4740
    Processor ID             : x86 Family 23 Model 49 Stepping 0, AuthenticAMD
    Session Key              : 0954a88e-2cb1-48a8-b561-fd1c1675a48c
    Window System            : Version 10.0 (Build 20348)

  Fault Count: 1

  Abnormal termination:
  Access violation

  Current Thread: 'MCR 0 interpreter thread' id 6640

  Register State (from fault):
    RAX = 0000000000000000  RBX = 000001c6593e5080
    RCX = 000001c64d827850  RDX = 00000042ac0eb560
    RSP = 00000042ac0eb3e0  RBP = 00000042ac0eb4e0
    RSI = 00000042ac0eb5e0  RDI = 000001c64d827850

     R8 = 000001c64d827850   R9 = 0000000000000001
    R10 = 0000000000000003  R11 = 00000042ac0eb220
    R12 = 00000042ac0ec168  R13 = 0000000000000000
    R14 = 00000042ac0eb560  R15 = 00000042ac0ec168

    RIP = 00007ffad53b8c0f  EFL = 00010246

     CS = 0033   FS = 0053   GS = 002b

  Stack Trace (from fault):
  [  0] 0x00007ffad53b8c0f C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\physmod_sm_gui_app_jni.dll+00232463 mech2::FlexibleBody::InvalidId::operator=+00001215
  [  1] 0x00007ffad53b2563 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\physmod_sm_gui_app_jni.dll+00206179 mech2::gui::JavaDialogInterface::closeDialog+00000083
  [  2] 0x00007ffad4cc86b6 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\physmod_sm_sli_dialog.dll+01148598 sm_block_dialog_callback+00000486
  [  3] 0x00007ffad1e6e18f C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\builtins\physmod\sm\sli\mwphysmod_sm_sli_dialog_builtinimpl.dll+00057743 us_set_bundle_context_instance_com_mathworks_physmod_sm_sli_dialog_builtinimpl+00022079
  [  4] 0x00007ffad1e68b82 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\builtins\physmod\sm\sli\mwphysmod_sm_sli_dialog_builtinimpl.dll+00035714 us_set_bundle_context_instance_com_mathworks_physmod_sm_sli_dialog_builtinimpl+00000050
  [  5] 0x00007ffb5bc96476 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\builtin.dll+00156790 MathWorks::builtin::BuiltinFcn::invoke+00001174
  [  6] 0x00007ffb5d328494 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_dispatcher.dll+00361620 mdLoadModuleForPackageOrClass+00007524
  [  7] 0x00007ffb5d328625 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_dispatcher.dll+00362021 mdLoadModuleForPackageOrClass+00007925
  [  8] 0x00007ffb5d2db76e C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_dispatcher.dll+00046958
  [  9] 0x00007ffb5d2fd1ad C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_dispatcher.dll+00184749 Mfh_MATLAB_fn_impl::dispatch+00000045
  [ 10] 0x00007ffb5c960c74 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00330868 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00234740
  [ 11] 0x00007ffb5c96f1f0 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00389616 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00293488
  [ 12] 0x00007ffb58661f31 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+05709617 MathWorks::lxe::ReadOnlyXvaluePtr::operator=+00006049
  [ 13] 0x00007ffb58663529 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+057[152](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:154)41 MathWorks::lxe::ReadOnlyXvaluePtr::operator=+00011673
  [ 14] 0x00007ffb585ae138 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+04972856 MathWorks::lxe::printLxeProfStatsForFeature+00300760
  [ 15] 0x00007ffb585c8189 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+05079433 MathWorks::lxe::printLxeProfStatsForFeature+00407337
  [ 16] 0x00007ffb583b803b C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02916411 MathWorks::lxe::LXEConstants::IsIfElse+00525851
  [ 17] 0x00007ffb583bc644 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02934340 MathWorks::lxe::LXEConstants::IsY+00012980
  [ 18] 0x00007ffb583b9a91 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02923[153](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:155) MathWorks::lxe::LXEConstants::IsY+00001793
  [ 19] 0x00007ffb583bd785 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02938757 MathWorks::lxe::LXEConstants::IsY+00017397
  [ 20] 0x00007ffb583bda33 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02939443 MathWorks::lxe::LXEConstants::IsY+00018083
  [ 21] 0x00007ffb583bd388 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02937736 MathWorks::lxe::LXEConstants::IsY+00016376
  [ 22] 0x00007ffb583b9236 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02921014 MathWorks::lxe::LxeTypes::GetTypeXvalueOf+00000598
  [ 23] 0x00007ffb58486f43 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+03764035 MathWorks::lxe::SetEngineImplUnlinkFlagForAllCallsOnStack+00042979
  [ 24] 0x00007ffb5848aa50 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+03779152 MathWorks::lxe::SetEngineImplUnlinkFlagForAllCallsOnStack+00058096
  [ 25] 0x00007ffb5ca34a90 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+01198736 FeatureTestObservableWorkspace+00184240
  [ 26] 0x00007ffb5c99e776 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00583542 mwboost::archive::detail::pointer_oserializer<mwboost::archive::xml_oarchive,MathWorks::lxe::PreLineExecutionEvent>::save_object_ptr+00069206
  [ 27] 0x00007ffb5c9a018f C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00590223 mwboost::archive::detail::pointer_oserializer<mwboost::archive::xml_oarchive,MathWorks::lxe::PreLineExecutionEvent>::save_object_ptr+00075887
  [ 28] 0x00007ffb5c9fecb3 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00978099 mwboost::archive::detail::iserializer<mwboost::archive::text_iarchive,MathWorks::MatlabComponents::ComponentIdentifier>::load_object_data+00303411
  [ 29] 0x00007ffb5ca00df7 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00986615 mwboost::archive::detail::iserializer<mwboost::archive::text_iarchive,MathWorks::MatlabComponents::ComponentIdentifier>::load_object_data+00311927
  [ 30] 0x00007ffb5c9ffd4c C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00982348 mwboost::archive::detail::iserializer<mwboost::archive::text_iarchive,MathWorks::MatlabComponents::ComponentIdentifier>::load_object_data+00307660
  [ 31] 0x00007ffb4539a0df C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwsl_services.dll+02400479 slsv::mxw::WarningHandler::operator=+00002911
  [ 32] 0x00007ffb453aff30 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwsl_services.dll+02490160 CMatlabCommand::execute+00000176
  [ 33] 0x00007ffb453c0864 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwsl_services.dll+02558052 slsvEVAL_NoThrow+00000084
  [ 34] 0x00007ffb40d0c95f C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\sl_graphical_classes.dll+03787103 SafeBlockCallbackDispatch+00007439
  [ 35] 0x00007ffb40d0c6e4 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\sl_graphical_classes.dll+03786468 SafeBlockCallbackDispatch+00006804
  [ 36] 0x00007ffb40d0eedd C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\sl_graphical_classes.dll+03796701 CallbackSupport::notifySimulinkMCOSEvent+00001837
  [ 37] 0x00007ffb40d0cc2b C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\sl_graphical_classes.dll+03787819 CallbackSupport::executeBlockCallback+00000107
  [ 38] 0x00007ffb43f04b44 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwsimulink.dll+09521988 getRelatedParameters+00136788
  [ 39] 0x00007ffb3600d1df C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\SimulinkBlock.dll+00905695 SLBlock::EvalDlgPrms+00000303
  [ 40] 0x00007ffb3600cb9f C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\SimulinkBlock.dll+00904095 SLBlock::DeleteCallback+00000207
  [ 41] 0x00007ffb43ffadb3 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwsimulink.dll+10530227 IsSourceBlock+00021139
  [ 42] 0x00007ffb40cf62dd C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\sl_graphical_classes.dll+03695325 slGraph::CallBlockDeleteCallbacks+00000269
  [ 43] 0x00007ffb3600cb15 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\SimulinkBlock.dll+00903957 SLBlock::DeleteCallback+00000069
  [ 44] 0x00007ffb43ffadb3 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwsimulink.dll+10530227 IsSourceBlock+00021139
  [ 45] 0x00007ffb40cf62dd C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\sl_graphical_classes.dll+03695325 slGraph::CallBlockDeleteCallbacks+00000269
  [ 46] 0x00007ffb40a4a0b8 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\sl_graphical_classes.dll+00893112 NormalVariantControlVars::IsVariantControlVarsExistWithSTVAT+00001320
  [ 47] 0x00007ffb40a6113c C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\sl_graphical_classes.dll+00987452 SLRootBDDestroyer::doWork+00000796
  [ 48] 0x00007ffb43f25226 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwsimulink.dll+09654822 SlBdDomainListener::SlBdDomainListener+00005494
  [ 49] 0x00007ffb40a5fd9a C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\sl_graphical_classes.dll+00982426 SLRootBD::destroyBlockDiagram+00000266
  [ 50] 0x00007ffb40a4886e C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\sl_graphical_classes.dll+00886894 SLRootBD::CachedFixedStepSize+00000654
  [ 51] 0x00007ffb40a5c400 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\sl_graphical_classes.dll+00967680 SLRootBD::closeSystem+00001104
  [ 52] 0x00007ffb41211d1d C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\sl_graphical_classes.dll+09051421 SLRootPrm::FreeLoadedLibraries+00000333
  [ 53] 0x00007ffb41cec2b4 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\sl_link_bd.dll+01098420 sleInitModelConditions+00000436
  [ 54] 0x00007ffb4417c8d7 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwsimulink.dll+12110039 slstSetOutputPortRateID+00126999
  [ 55] 0x00007ffb441823e2 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwsimulink.dll+12133346 slstSetOutputPortRateID+00150306
  [ 56] 0x00007ffb44189fe3 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwsimulink.dll+12165091 slstSetOutputPortRateID+00182051
  [ 57] 0x00007ffb441896cf C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwsimulink.dll+12162767 slstSetOutputPortRateID+00179727
  [ 58] 0x00007ffb441c3673 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwsimulink.dll+12400243 slstSetOutputPortRateID+00417203
  [ 59] 0x00007ffb43b7ace6 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwsimulink.dll+05811430 slAccRegPrmChangeFcn+00093014
  [ 60] 0x00007ffb43add1c7 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwsimulink.dll+05165511 slFullSimulate+00000503
  [ 61] 0x00007ffb457992aa C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\sl_proxy_interface.dll+00037546 wrapper_matl_sim+00000074
  [ 62] 0x00007ffb457c2d8f C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\builtins\sl_proxy_interface\mwsl_proxy_interface_builtinimpl.dll+00077199 us_set_bundle_context_instance_com_mathworks_sl_proxy_interface_builtinimpl+00041535
  [ 63] 0x00007ffb457b8ba2 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\builtins\sl_proxy_interface\mwsl_proxy_interface_builtinimpl.dll+00035746 us_set_bundle_context_instance_com_mathworks_sl_proxy_interface_builtinimpl+00000082
  [ 64] 0x00007ffb5bc96476 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\builtin.dll+00[156](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:158)790 MathWorks::builtin::BuiltinFcn::invoke+00001174
  [ 65] 0x00007ffb5d328494 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_dispatcher.dll+0036[162](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:164)0 mdLoadModuleForPackageOrClass+00007524
  [ 66] 0x00007ffb5d328625 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_dispatcher.dll+00362021 mdLoadModuleForPackageOrClass+00007925
  [ 67] 0x00007ffb5d2db76e C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_dispatcher.dll+00046958
  [ 68] 0x00007ffb5d2fd1ad C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_dispatcher.dll+00184749 Mfh_MATLAB_fn_impl::dispatch+00000045
  [ 69] 0x00007ffb5c960c74 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00330868 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00234740
  [ 70] 0x00007ffb5c96f1f0 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00389616 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00293488
  [ 71] 0x00007ffb58661f31 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+05709617 MathWorks::lxe::ReadOnlyXvaluePtr::operator=+00006049
  [ 72] 0x00007ffb58663529 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+05715241 MathWorks::lxe::ReadOnlyXvaluePtr::operator=+00011673
  [ 73] 0x00007ffb585ae138 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+04972856 MathWorks::lxe::printLxeProfStatsForFeature+00300760
  [ 74] 0x00007ffb585c8189 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+05079433 MathWorks::lxe::printLxeProfStatsForFeature+00407337
  [ 75] 0x00007ffb583b803b C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02916411 MathWorks::lxe::LXEConstants::IsIfElse+00525851
  [ 76] 0x00007ffb583bc644 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02934340 MathWorks::lxe::LXEConstants::IsY+00012980
  [ 77] 0x00007ffb583b9a91 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02923153 MathWorks::lxe::LXEConstants::IsY+00001793
  [ 78] 0x00007ffb583bd785 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02938757 MathWorks::lxe::LXEConstants::IsY+00017397
  [ 79] 0x00007ffb583bda33 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02939443 MathWorks::lxe::LXEConstants::IsY+00018083
  [ 80] 0x00007ffb583bd388 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02937736 MathWorks::lxe::LXEConstants::IsY+000[163](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:165)76
  [ 81] 0x00007ffb583b9236 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02921014 MathWorks::lxe::LxeTypes::GetTypeXvalueOf+00000598
  [ 82] 0x00007ffb58486f43 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+03764035 MathWorks::lxe::SetEngineImplUnlinkFlagForAllCallsOnStack+00042979
  [ 83] 0x00007ffb5848aa50 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+03779152 MathWorks::lxe::SetEngineImplUnlinkFlagForAllCallsOnStack+00058096
  [ 84] 0x00007ffb5ca34a90 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+01198736 FeatureTestObservableWorkspace+00184240
  [ 85] 0x00007ffb5c959d73 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00302451 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00206323
  [ 86] 0x00007ffb5c9594a3 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00300195 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00204067
  [ 87] 0x00007ffb5c95baa2 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00309922 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00213794
  [ 88] 0x00007ffb5d3cda32 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_dispatcher.dll+01038898 Mfh_file::dispatch_file_common+00000[178](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:180)
  [ 89] 0x00007ffb5d3ccd02 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_dispatcher.dll+01035522 Mfh_error::lookup+00012722
  [ 90] 0x00007ffb5d3cd96d C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_dispatcher.dll+01038701 Mfh_file::dispatch+00000045
  [ 91] 0x00007ffb5c960c74 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00330868 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00[234](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:236)740
  [ 92] 0x00007ffb5c96f1f0 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00389616 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00293488
  [ 93] 0x00007ffb58661f31 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+05709617 MathWorks::lxe::ReadOnlyXvaluePtr::operator=+00006049
  [ 94] 0x00007ffb58663529 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+05715241 MathWorks::lxe::ReadOnlyXvaluePtr::operator=+00011673
  [ 95] 0x00007ffb585ae138 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+04972856 MathWorks::lxe::printLxeProfStatsForFeature+00300760
  [ 96] 0x00007ffb585c8189 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+05079433 MathWorks::lxe::printLxeProfStatsForFeature+00407337
  [ 97] 0x00007ffb583b803b C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02916411 MathWorks::lxe::LXEConstants::IsIfElse+00525851
  [ 98] 0x00007ffb583bc644 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02934340 MathWorks::lxe::LXEConstants::IsY+00012980
  [ 99] 0x00007ffb583b9a91 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02923153 MathWorks::lxe::LXEConstants::IsY+00001793
  [100] 0x00007ffb583bd785 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02938757 MathWorks::lxe::LXEConstants::IsY+00017397
  [101] 0x00007ffb583bda33 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02939443 MathWorks::lxe::LXEConstants::IsY+00018083
  [102] 0x00007ffb583bd388 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02937736 MathWorks::lxe::LXEConstants::IsY+00016376
  [103] 0x00007ffb583b9236 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02921014 MathWorks::lxe::LxeTypes::GetTypeXvalueOf+00000598
  [104] 0x00007ffb58486f43 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+03764035 MathWorks::lxe::SetEngineImplUnlinkFlagForAllCallsOnStack+00042979
  [105] 0x00007ffb5848aa50 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+03779152 MathWorks::lxe::SetEngineImplUnlinkFlagForAllCallsOnStack+00058096
  [106] 0x00007ffb5ca34a90 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+01198736 FeatureTestObservableWorkspace+00184240
  [107] 0x00007ffb5c959d73 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00302451 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00206323
  [108] 0x00007ffb5c9594a3 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00300195 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00204067
  [[109](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:111)] 0x00007ffb5c95baa2 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00309922 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00213794
  [[110](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:112)] 0x00007ffb5d3cda32 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_dispatcher.dll+01038898 Mfh_file::dispatch_file_common+00000178
  [[111](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:113)] 0x00007ffb5d3ccd02 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_dispatcher.dll+01035522 Mfh_error::lookup+00012722
  [[112](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:114)] 0x00007ffb5d3cd96d C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_dispatcher.dll+01038701 Mfh_file::dispatch+00000045
  [[113](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:115)] 0x00007ffb5c960c74 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00330868 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00234740
  [[114](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:116)] 0x00007ffb5c96f1f0 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\libmwlxemainservices.dll+00389616 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00293488
  [[115](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:117)] 0x00007ffb58661f31 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+05709617 MathWorks::lxe::ReadOnlyXvaluePtr::operator=+00006049
  [[116](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:118)] 0x00007ffb58663529 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+05715241 MathWorks::lxe::ReadOnlyXvaluePtr::operator=+00011673
  [[117](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:119)] 0x00007ffb585ae138 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+04972856 MathWorks::lxe::printLxeProfStatsForFeature+00300760
  [[118](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:120)] 0x00007ffb585c8189 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+05079433 MathWorks::lxe::printLxeProfStatsForFeature+00407337
  [[119](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:121)] 0x00007ffb583b803b C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02916411 MathWorks::lxe::LXEConstants::IsIfElse+00525851
  [[120](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:122)] 0x00007ffb583bc644 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02934340 MathWorks::lxe::LXEConstants::IsY+00012980
  [[121](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:123)] 0x00007ffb583b9a91 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02923153 MathWorks::lxe::LXEConstants::IsY+00001793
  [[122](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:124)] 0x00007ffb583bd785 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02938757 MathWorks::lxe::LXEConstants::IsY+00017397
  [[123](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:125)] 0x00007ffb583bda33 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02939443 MathWorks::lxe::LXEConstants::IsY+00018083
  [[124](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:126)] 0x00007ffb583bd388 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02937736 MathWorks::lxe::LXEConstants::IsY+00016376
  [[125](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:127)] 0x00007ffb583b9236 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+02921014 MathWorks::lxe::LxeTypes::GetTypeXvalueOf+00000598
  [[126](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:128)] 0x00007ffb58486f43 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+03764035 MathWorks::lxe::SetEngineImplUnlinkFlagForAllCallsOnStack+00042979
  [[127](https://github.com/H0R5E/WEC-Sim/actions/runs/4183444880/jobs/7247809822#step:6:129)] 0x00007ffb5848aa50 C:\hostedtoolcache\windows\MATLAB\9.13.0\x64\bin\win64\m_lxe.dll+03779152 MathWorks::lxe::SetEngineImplUnlinkFlagForAllCallsOnStack+00058096

  ** This crash report has been saved to disk as C:\Users\RUNNER~1\AppData\Local\Temp\matlab_crash_dump.4740-1 **

  MATLAB is exiting because of fatal error
  ERROR: MATLAB error Exit Status: 0xc0000005, Access violation
  exit status 0xc0000005
Error: Error: The process 'D:\a\_actions\matlab-actions\run-command\v1\dist\bin\win64\run-matlab-command.exe' failed with exit code 1

Many thanks for your help,

Mat

davidbuzinski commented 1 year ago

Thanks for this! I just added Windows to my CI with the Fixed-Point Designer toolbox, and it works.

Two things I noted though.

1. I get a warning when it just uses the latest release (doesn't seem related to the toolbox specification though)
Run matlab-actions/setup-matlab@v2-beta
  with:
    products: Fixed-Point_Designer
    release: latest
Setting up MATLAB
  "C:\Program Files\PowerShell\7\pwsh.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command "$ErrorActionPreference = 'Stop' ; try { Add-Type -AssemblyName System.IO.Compression.ZipFile } catch { } ; try { [System.IO.Compression.ZipFile]::ExtractToDirectory('D:\a\_temp\53078015-7b71-4c5c-8782-6c1d4a2a6877', 'D:\a\_temp\6978282d-4f7f-462f-84c9-f2b6b0643dad', $true) } catch { if (($_.Exception.GetType().FullName -eq 'System.Management.Automation.MethodException') -or ($_.Exception.GetType().FullName -eq 'System.Management.Automation.RuntimeException') ){ Expand-Archive -LiteralPath 'D:\a\_temp\53078015-7b71-4c5c-8782-6c1d4a2a6877' -DestinationPath 'D:\a\_temp\6978282d-4f7f-462f-84c9-f2b6b0643dad' -Force } else { throw $_ } } ;"
  "C:\Program Files\Git\usr\bin\chmod.exe" +x D:\a\_temp\6978282d-4f7f-462f-84c9-f2b6b0643dad\bin\win64\mpm.exe
  D:\a\_temp\6978282d-4f7f-462f-84c9-f2b6b0643dad\bin\win64\mpm.exe install --release=r2022blatest --destination=C:\hostedtoolcache\windows\MATLAB\9.13.0\x64 --products Fixed-Point_Designer MATLAB Parallel_Computing_Toolbox
  Warning: Invalid syntax of update level, using latest update for R2022b.
2. Capitalization of the toolboxes/products matter (I don't know if it is just me, but I first tried all lowercase instead since that was what came naturally to me).

Hi @imciner2,

Thanks for the feedback! We have updated so that the warning message you see for latest release is fixed. In regards to capitalization mattering in the products list, I agree that it is unintuitive, but we are not able to change it at this time. I'll make sure that feedback is passed along.

davidbuzinski commented 1 year ago

Hi @H0R5E,

I talked to some folks from Simscape Multibody and it sounds like the crash you are seeing has something to do with how MATLAB interacts with the display when run on Windows in the CI environment. I was able to reproduce it, and it is avoidable if MATLAB is launched with the -noFigureWindows startup option.

We don't currently support passing startup options to MATLAB when running our actions, but it is something we are currently looking into. I will reply here if/ when that feature is added. It is also possible that this will be fixed in an update or future release of MATLAB, and no startup option will be required.

H0R5E commented 1 year ago

@davidbuzinski, thanks for the feedback, again!

Would it not be possible just to call MATLAB using batch mode and the -noFigureWindows option? Something like:

- run: matlab -noFigureWindows -batch some_file
H0R5E commented 1 year ago

@davidbuzinski, from my own testing I guess the answer to my question is no!

License checkout failed.
License Manager Error -1
The license.dat file cannot be found.
acampbel commented 1 year ago

This starts to get into implementation detail which may be fragile, but you may be able to run the following command;

- run: matlab-batch some_file -noFigureWindows

H0R5E commented 1 year ago

@acampbel, thanks for your reply. I'm afraid this command doesn't work for me, I just get the following:

ERROR: missing input: token
kmruehl commented 1 year ago

Thanks @H0R5E for tracking this discussion. Is there any update? We'd like to run our WEC-Sim tests with MATLAB on Windows.

mcafaro commented 1 year ago

The latest version of matlab-actions/run-command@v1 (v1.2) now has a startup-options input where you can include -noFigureWindows:

- name: Run command
  uses: matlab-actions/run-command@v1
  with:
    command: mycommand
    startup-options: -noFigureWindows

Note: -noFigureWindows is available only on Windows.

kmruehl commented 1 year ago

Thank you! We look forward to using this feature for our tests. Much appreciated.