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.

Sign up for GitHub

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

Jump to bottom

Investigate occasional Travis failures #160

Open
yurrriq opened this issue Mar 1, 2016 · 2 comments
Open

Investigate occasional Travis failures #160

yurrriq opened this issue Mar 1, 2016 · 2 comments
Labels
contributor friendly

Comments

@yurrriq
Copy link
Collaborator

yurrriq commented Mar 1, 2016 

ERROR in (set-semigroup) (:)
Uncaught exception, not in assertion.
expected: nil
  actual: #object[RangeError RangeError: Maximum call stack size exceeded]

I had to leave the tests running for 10 minutes before it occurred for me locally. I think it depends on the seed given to quick-check, which unfortunately isn't printed when tests fail.

– @sfnelson's comment
@yurrriq
Copy link
Collaborator Author

yurrriq commented Mar 1, 2016

It might be worth tweaking --stack-size. I had to do something similar wrt property-based testing on an LFE project.

@ghost
Copy link

ghost commented Mar 1, 2016

I'm afraid that it is because how generators work, I'm happy to enlarge the node's stack size for running the tests to avoid this 👍

@ghost ghost added the contributor friendly label Mar 1, 2016
@yurrriq yurrriq mentioned this issue Mar 22, 2016
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
contributor friendly
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yurrriq