-
Notifications
You must be signed in to change notification settings - Fork 8
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
Fix: local checkfile used in testing is now general enough #69
Conversation
…t from breaking when source of chasten changes
8af0c93
to
d12e0b7
Compare
these checks were hindering our build. They serve no semantic purpose, so it is completely appropriate to remove them.
It appears that we're having problems with coverage here. I'll continue to look into this and comment what I find here. I was not expecting this. @laurennevill |
Hopefully fixes the pip install issue on windows
Hey @gkapfham, this is priority one for merges |
The problem with coverage is still unidentified and unsolved, just letting this thread know. |
fix: update pip command
@laurennevill @gkapfham , Mordred and I found that the failing checks is a transient issue. I suspect that, because coverage is time consuming, the process is timing out, but this does not appear to be obvious anywhere. Regardless, we have proven that the issue is not consistent, and we both recommend merging this when possible. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job working so hard on this over the past few weeks. Hopefully this will be one step closer to a better build!
Previously, the local checkfile
.chasten/checks.yml
had checks searching for things like doubly-nestedif
statements found in thechasten
source code. Because finding things like this in our repository source code is not set in stone, I have changed this to be general enough to effectively test the functionality without making false assumptions such as the one previously mentioned.Closes #59
NOTE: depends on #68 before merging.
NOTE: @gkapfham is pointing out that #68 has now been merged.