Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add CI test for Windows with GitHub actions #48
base: winport
Are you sure you want to change the base?
Add CI test for Windows with GitHub actions #48
Changes from all commits
57531d6
3ac85e4
ecbb347
f6c0551
de964e2
c9f2bdf
5cd98d8
95fe0bc
a415140
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
bash
exists on Windows only when WSL is installed. It may take 10 seconds to boot the lightweight WSL VM, and file access is fairly slow from inside of the VM to files outside of its VHD. I'd usecmd
if I were you. The default on Windows ispwsh
. Verify that the VS command line environment is set up in the worker:I'm getting
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 is quite fast in GitHub actions and you won't feel any latency between
cmd
andbash
.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.
I still strongly suggest switching to the native shell. I know what is going on in the guts of the OS when you use WSL Bash this way, and that's a lot, and I do mean a lot. A hypervisor partition is created, then a network switch, a Linux OS is booted into this partition from a .vhd virtual disk, then it mounts Windows volumes using the
9p
filesystem over a virtual network, and it maps Linuxrwxrwxrwx
attributes to Windows' ACLs in a tricky way, also depending on whether and how WSL is configured in its/etc/wsl.conf
... An upgrade to WSL may easily break it in a spectacular way. If Microsoft says don't do it, I better don't.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.
Please see the following error after switching to
cmd
andNinja
:https://github.com/csukuangfj/openfst/actions/runs/8794917596/job/24135134756#step:4:4
I want to point out that the main purpose of GitHub actions is to check that the code compiles and runs.
It does not matter whether
cmd
orbash
, orNinja
is used. The time for building in GitHub actions can be ignored, though I have never noticed usingcmd
orNinja
in GitHub actions brings speedup in building.