-
Notifications
You must be signed in to change notification settings - Fork 57
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
Support go-mutesting on Windows #58
Comments
Are you using windows? |
Yes, that was run on a Windows Machine. |
I am really sorry but I do not have a Windows machine to try to solve this. Can you help me? |
Got it working! :) I was trying to reach your tool for some research, but am using Windows, and more importantly, I'm clueless about Go tooling.... So I set out on a small journey to get this working. Compiling on Windows itself is annoying, but luckily Go supports easy cross-compilation. So I could compile in a docker container for Windows. Unfortunately, when trying that, you get errors about But..... I noticed prestonvanloon@3a7f002 in a fork, that seems interesting! So I applied it locally, but Go will in some places just pull in github.com/zimmski/go-mutesting, and not use the "in-repo" Then I took a very blunt approach, and I'm want to hear if this overkill or wrong @zimmski !, I just replaced your username with mine everywhere, pushed my changes to my fork and it worked. So, at the root of the repo (my fork), run: |
(Actually I know it's overkill to replace everywhere (especially README), but it was easiest and I'm out of time for today....) |
(Sorry for the spam) It doesn't really seem to work 👎 There doesn't have to be any compilation of the mutated source code if I specify --no-exec right? I'm trying to mutate the docker/engine source but gets hundreds of errors like
Will now move to just doing things completely in a container, bit clumsy but ok. edit: Switched to Go 1.11.1 , then something like this seems to work for some part:
|
@afraca: The usual workflow I use when I fork a project for doing a PR to said project is: Checkout the project in the correct subdirectory (e.g. ~/go/src/github.com/zimmski/go-mutesting on my computer), then add a "fork" git "remote" to the repository, and then work with branches pushed to the fork repository. This makes it possible to use the correct namespace/path even though it is not a repository you have write access to. |
@afraca: The osutil problem should be already solved. So please give it another whirl! |
@afraca: The "no-exec" option should generate all mutations for the given package(s) but should not execute any test suite. I tried the "no-exec" option with |
Go get fails for me:
The text was updated successfully, but these errors were encountered: