| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
This decorator enabled us to use the functionality of the Actions toolcache within the runner too. Now that we've deleted the runner we no longer need it.
There was a problem hiding this comment.
This looks sensible. I just have a few questions inline so I can understand what is going on.
Sorry, something went wrong.
| // Workaround an issue in tests where the case insensitivity of the `$PATH` | ||
| // environment variable on Windows isn't preserved, i.e. `process.env.PATH` | ||
| // is not the same as `process.env.Path`. |
There was a problem hiding this comment.
That's wild. When does this happen?
Sorry, something went wrong.
There was a problem hiding this comment.
I spent a while looking into this, but couldn't track down what was going on. My suspicion is that this weirdness might have something to do with how we use an assignment to process.env to reset it at the end of every test to its value at the start of the test.
Sorry, something went wrong.
`toolcache.extractTar` currently falls over when `ACTIONS_TEMP` contains a symlink, and the runner no longer exists, so it's unlikely our customers would be running with temporary directories that contain symlinks.
| Back | FazBrowse Home | New Git URL |
This PR runs our unit tests on Windows, primarily to improve test coverage but also to support developing the Action on Windows machines. In doing so, we fix a couple of bugs.
For review: I spent a while looking at whether we could avoid the ugly hack in 6063828, however couldn't find anything. Do you have any thoughts?
Based on #1104.
Merge / deployment checklist