Skip to content
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

Crashes Ruby when used with mutant gem #72

Open
tjchambers opened this issue Aug 18, 2015 · 4 comments
Open

Crashes Ruby when used with mutant gem #72

tjchambers opened this issue Aug 18, 2015 · 4 comments

Comments

@tjchambers
Copy link

Just an FYI I started to use this gem latest version yesterday and was pleased with it's benefits.

However I am heavily using mutation testing (mbj/mutant) of whom @dkubb is a contributor as well. I am a relative noobie. When I run my test suite after installing this gem it crashes Ruby 2.2 (appears to run out of stack). I have 100's of crash dumps and misbehavior documented in my mutation logs. When I remove the gem from the bundle normal behavior returns. It does not appear to be related to adding "normalize_attributes" statements. I spent a couple hours trying to get a simplified reproducible repo, but was not able too.

I am not blaming this gem as I don't know whether it is concurrency in mutant, or something this gem is doing inside a forked environment. I just really do not know.

I can say that in resurveying the landscape of gem's with this ones' functionality I ran across normalizr and replaced attribute_normalizer with that gem and got satisfactory functionality as well as it did not crash Ruby when running mutation testing.

Just a caution. If you want more detail I would be more than happy to add some gists with the crash dumps. I just wanted to make you aware of this.

@mdeering
Copy link
Owner

Thanks for the heads up. I would love play around with a repository having these issues to dig around myself as I am planning a rewrite in the not to distant future. I have used this gem on projects in the past that also include mutant but I can not recall what version of either I was running.

@tjchambers
Copy link
Author

I spent a lot of time trying to get a simple reproduction, and for my limited knowledge I was unable to get it to repro with something I could push for you to test. I feel badly since I hate leaving these issues - especially a ruby crash - as unreproducible and mysterious. However if you do get a chance to try it on your test suite yourself (I did not) under mutant it may surface. If you think I can help or want my crash info, I will be happy to provide.

@tjchambers
Copy link
Author

One piece of information is that mutant went from killing mutations to reporting unkilled specs on unmutated values with the test output = "marshal data too short". That was the only information from mutant itself, but my console was reporting crash dumps once per second.

@mdeering
Copy link
Owner

mdeering commented Dec 4, 2019

I have run many projects with these two gems alongside each other without issue.

I will add look at adding mutant to this test suite as it is pretty fast and could potentially add some value to the suite as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants