| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Bumps [Vampire/setup-wsl](https://github.com/vampire/setup-wsl) from 3.0.0 to 3.1.0. - [Release notes](https://github.com/vampire/setup-wsl/releases) - [Commits](Vampire/setup-wsl@v3.0.0...v3.1.0) --- updated-dependencies: - dependency-name: Vampire/setup-wsl dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
|
There appear to be two separate kinds of failures here. The failure with Python 3.7 on Ubuntu appears to be a result of a corrupted download, which should resolve if re-run. In contrast, it seems the failures on Windows always occur with that step, as written, to install Debian, at least on windows-latest, as shown in this much-simplified testing repository. I've opened Vampire/setup-wsl#58 to report that. Although we should probably wait for feedback on Vampire/setup-wsl#58 (and possibly a fix) before attempting further steps toward bringing in the changes from this PR, I suggest rerunning all pythonpackage.yml tests here, to check that my prediction is correct. It may not be strictly necessary to do so, since I have made a branch in my fork from this branch here, whose CI does behave that way. But rerunning them all here should give slightly greater confidence and, perhaps more importantly, should make it clearer, when we (or others, perhaps to fix the issue) look at this later, which test jobs fail consistently. |
Sorry, something went wrong.
|
The setup-wsl problem should be fixed in 3.1.1, sorry |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM. It is working since 3.1.1 was released and this was further bumped to it, so I think this can be merged.
Although Dependabot could be made to redo the version update in which case the PR title its commit message would have 3.1.1-specific links, I think that's not necessary and the manual bump, as already done here, is sufficient. The commit history will make clear that the action was upgraded to 3.1.1. (If you do want to do that, I think just having Dependabot redo the version update scan with the "Check for updates" button in "Recent update jobs" would be sufficient; I believe that would cause Dependabot to close this PR and open another one. I emphasize that I am not requesting this.)
Some subsequent changes may make sense, such as changing Debian to Alpine. As discussed in #1745, this was waiting on Vampire/setup-wsl#50, which is now fixed. However, since the value of upgrading is not contingent on that, I recommend merging this PR first. Afterwards, I can experiment with and, if it seems helpful, open a PR to change Debian to Alpine.
Sorry, something went wrong.
|
Thanks everyone! I went ahead and just merged this PR, and hope it helps. |
Sorry, something went wrong.
Some of the CI tests use WSL. This switches the WSL distribution from Debian to Alpine, which might be slightly faster. For the way it is being used here, the main expected speed improvement would be to how long the image would take to download, as Alpine is smaller. (The reason for this is thus unrelated to the reason for the Alpine docker CI test job added in gitpython-developers#1826. There, the goal was to test on a wider variety of systems and environments, and that runs the whole test suite in Alpine. This just changes the WSL distro, used by a few tests on Windows, from Debian to Alpine.) Two things have changed that, taken together, have unblocked this: - Vampire/setup-wsl#50 was fixed, so the action we are using is able to install Alpine Linux. See: gitpython-developers#1917 (review) - gitpython-developers#1893 was fixed in gitpython-developers#1888. So if switching the WSL distro from Debian to Alpine breaks any tests, including by making them fail in an unexpected way that raises the wrong exception, we are likely to find out.
| Back | FazBrowse Home | New Git URL |
Bumps Vampire/setup-wsl from 3.0.0 to 3.1.0.
Release notesSourced from Vampire/setup-wsl's releases.
CommitsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: