-
Notifications
You must be signed in to change notification settings - Fork 587
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
Ruby tests failing for Python PR #1351
Comments
Given how much flakiness we're seeing with the Python build, I'm not sure the Ruby build is likely to be more of a problem here than the Python build. The real question is why these tests are being run here at all. The |
FWIW, to check for file changes in the Wellcome repo, I use $ git diff --name-only [...] and run checks against the list of files I get back. (Yes you shouldn't assume filenames don't contain newlines and splitting a list of filenames on newlines is bad, but in a repo with moderately sensible devs this is good enough.) That allows our Travis scripts to dump an explanation of why they did or didn't run tests. I find that helpful when I'm fine-tuning the logic, maybe something similar would be helpful here?
|
Blame that on the sudden increase in test power thanks to #1295 - it turns out that a handful of tests reliably passed, but only because we almost always explored the same states. This should calm down soon, once we improve the remaining test issues (e.g. #1348, and discussed in #1330). More specifically, I'm happy to call this issue closed by #1354. |
https://travis-ci.org/HypothesisWorks/hypothesis/jobs/396075133 failed while building #1282. Perhaps we should force-pass Ruby tests for PRs that don't touch hypothesis-ruby/ until it leaves alpha?
The text was updated successfully, but these errors were encountered: