-
Notifications
You must be signed in to change notification settings - Fork 4
Update run-matlab-command compression #132
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
Conversation
…ension into update-rmc-compression
| tr.registerMock("fs", { | ||
| chmodSync: () => Promise.resolve(0), | ||
| }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huh, was this failing before? Or did it just work even with that not mocked out?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was working. It was just operating on the actual file. This time the file didn't exist (because it needs to be unzipped) so it was failing. I wanted to make sure our tests don't ever actually unzip anything so we don't accidentally ship both the zip and the unzipped binary
This change is so that we no longer rely on
upxto compress therun-matlab-commandbinary. We were doing this in order to get our extension below the size limit to publish on the marketplace.It is updated to zip all of the run-matlab-command binaries that we ship in the extension. During all of the "run" steps, we will unzip the binary if it hasn't already been unzipped. It adds a small amount of overhead and maintenance, but ensures that we do not add any further external dependencies onto the runner for our Tasks.
I am also commenting out the failing parallel tests steps until the issue mentioned in the comment is resolved.