-
Notifications
You must be signed in to change notification settings - Fork 187
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
Stryker fails to connect to vstest on M1 mac #2117
Comments
Could you see if you have any vstest logs in the log directory? |
I have only 1 log file under the test_folder/Stryker Output/date/logs and you can find it in the description section. |
Did you run stryker with There should be some log files like
|
Yeap, I ran |
The library we use to connect to vstest.console should have it's own logfile, I expected that log file to be there containing with some hint as to why connection to vstest.console failed. Seems that it has not managed to even do that. Unfortunately I do not have a Mac. I think @dupdob has a mac but he has not reported such issues so I doubt they have them. I think it could be that theirs is not an M1 mac. I have a feeling this might be related to M1 macs. In that case we cannot troubleshoot this for you unfortunately. I think at this point the best course of action is to report this issue over on https://github.com/microsoft/vstest. I could report the issue for you so it has some details on how we integrate with vstest but they will likely ask us to provide some diagnostics or do some tests for us which we cannot do since we cannot currently reproduce this. Do you think this is something you could assist with after we report the issue with them? |
Thanks a lot! |
hi |
I just made a check, ran smoothly on my intel Mac (MBP2020) on Ventura (MacOS 13). |
for info: I added some logs (in my current PR) as an attempt to get some details on why VsTest fails to start. |
I am also getting VsTest console timeout errors, as described. I'm on a HP Z-Book running Windows 10. |
hi @libravado |
@dmitryvorobey I am rolling a new version (2.1.2) where we should get a little more information from the exception that is thrown that could perhaps help us move forward. It should be released within the next hour. If you have time I would appreciate it if you could give it a try and report back with the actual exception. |
@dmitryvorobey any chance you could help us out here? |
I was unable to reproduce this issue on my M1 macbook pro (2020, 16GB) running macOS 12.4. I ran Stryker succesfully on a few projects, and did not encounter any issues. Let me know if I can test projects more specific to this issue. |
In that case and since we have had no further reports I will close the issue as not reproducible. Thank you! |
Describe the bug
Hi guys! I've tried to install the Stryker and run it from the test's directory but it was unsuccessful.
Error message is "Stryker failed to connect to vstest.console"
Is it a bug or I doing smth wrong?
Logs
Probably it the most useful part of logs
[16:35:39 DBG] Initial build successful
[16:35:39 DBG] VsTest zip was copied to: /var/folders/0d/kw0r8pcx1rn06j4d2g_bmjj00000gn/T/o2gew0gf.rrm/.vstest/vstest.zip
[16:35:39 DBG] VsTest zip was unzipped to: /var/folders/0d/kw0r8pcx1rn06j4d2g_bmjj00000gn/T/o2gew0gf.rrm/.vstest
[16:35:39 DBG] Using vstest from deployed vstest package
[16:35:39 DBG] Using vstest.console: OSX for OS /var/folders/0d/kw0r8pcx1rn06j4d2g_bmjj00000gn/T/o2gew0gf.rrm/.vstest/tools/netcoreapp2.1/vstest.console.dll
[16:35:39 INF] Time Elapsed 00:00:03.4676349
Unhandled exception.
Stryker failed to connect to vstest.console
log-20220727.txt
Expected behavior
Stryker should successful mutate code and run tests
Desktop (please complete the following information):
Additional context
Macbook M1
The text was updated successfully, but these errors were encountered: