-
Notifications
You must be signed in to change notification settings - Fork 6
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
Local failure of "make test-lite" #53
Comments
Martin- would appreciate your advice here but I really don't think there's any alternative if the test suite is going to actually test the PUF flat file data creation, given we cannot publish the PUF microdata. Even if we're not pulling it from PolicyEngine-US's repo, we will need to pull from a different repo because GitHub doesn't support private data releases on public repos. In any case, I've just emailed you the token though. |
@nikhilwoodruff, Thanks for sending me the token. Using it allowed me to run successfully the You're correct about the need for this given the privacy-status of the PUF data. However, it seems as if adding a note (say to the README.md file) that alerts people to the need for a token would be helpful. Otherwise, they will be puzzled about why the simplest test doesn't work. Also, is it possible to define a narrower test that can be run without a token? |
Thanks @martinholmer- I've added a note to the Readme in #52. |
@nikhilwoodruff said:
Thanks! That's perfect. |
After updating the the repository and executing
make install-lite
, I tried to executemake test-lite
on my computer. It doesn't seem right that the simplest test in an open-source repository should require a "token" to access data in a different (Policyengine-US) repository.Here is what happens on my computer:
The text was updated successfully, but these errors were encountered: