-
Notifications
You must be signed in to change notification settings - Fork 250
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
Beta: Stryker can get confused by its own reports directory #2466
Comments
check for sure if you have good packages, i can see some 3.3.1 versions here. + i think we are not using transpilers now (i dunno if it beta.4 tho). Also please provide full stryker.log file :) and if possible it is helpful when you have some reproductive repo (unless its private or something) so its easier for us to debug :) |
I pointed you to the repo I am running against, which together with the config file is everything you would need to repro (except for bug 2465, which I had to work around - the modified repo is at this fork/branch: https://github.com/gramster/vscode-python-me/tree/stryker). I can see that the Stryker process is still consuming CPU but I don't know what it is doing. Full log file is too large to attach but I don't think it will tell you anything more useful than what I posted above. Some of the old packages are there because I started with Stryker 3 and then switched to beta; I don't think they should have any impact but I can remove them. |
I removed all the Stryker packages and then ran:
which resulted in:
and stryker still gets stuck. |
I broke in with a debugger and got this call stack: It turned out it was stuck trying to process files created by Stryker itself in the reports/ directory. After deleting that folder it started making progress again. Stryker should probably be ignoring that directory. It failed shortly after:
|
Awesome work you're doing here @gramster This is helping us a lot 🎉
I think this is a bit "by design" 😅 . We're currently using your own As for the EDIT: Just did a new release: What we're basically doing, is create TS compile errors. No way around that, since we're instrumenting your TS code with mutants. To disable type checks, we're adding For example: {
"disableTypeChecks": "**/*.ts"
} |
@gramster I think this can be closed, or is there still something to be done here? |
Closing this for now. Don't hesitate to contact me if you think it is a mistake 👍 |
Question
I'm making this a question for now but perhaps it should be labelled a bug. I'm using the beta, and worked around the issue #2465 for now, but now after instrumentation nothing happens. I have detailed logging on, and I left it running for hours, but the last thing in the log is:
and nothing happens after that.
Config:
This is for the Python extension for Visual Studio Code, so it should be reproducable.
It's very possible that my configuration is not right, but I still wouldn't expect a hang like this.
Stryker environment
Additional context
I haven't added any config for the typescript checker as the build command makes use of multiple tsconfig files for different parts of the code.
The text was updated successfully, but these errors were encountered: