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

How to avoid GitHub test failures? #56

Closed
martinholmer opened this issue Apr 23, 2024 · 9 comments
Closed

How to avoid GitHub test failures? #56

martinholmer opened this issue Apr 23, 2024 · 9 comments
Labels
question Further information is requested

Comments

@martinholmer
Copy link
Collaborator

Related to issue #53.

@nikhilwoodruff
Copy link
Collaborator

@martinholmer- you'll need to file pull requests from branches on the repo rather than forks (otherwise, anyone could obtain the PUF by forking the repo). Sorry for not mentioning this- I'll add this to the README.

@martinholmer
Copy link
Collaborator Author

@nikhilwoodruff said in issue #56:

you'll need to file pull requests from branches on the repo rather than forks

Thanks for the tip, but I have no idea how to do that. Can you provide more details?

@MaxGhenis
Copy link

@martinholmer
Copy link
Collaborator Author

@MaxGhenis said in issue #56:

As an example, you'd clone https://github.com/PSLmodels/tax-microdata-benchmarking instead of https://github.com/martinholmer/tax-microdata-benchmarking

If I can do that, what prevents anybody else from doing that, and therefore, getting access to the private PUF data? What am I missing?

@martinholmer martinholmer added the question Further information is requested label May 5, 2024
@martinholmer martinholmer changed the title GitHub test failures because it does not know the Policyengine-US TOKEN How to avoid GitHub test failures? May 5, 2024
@MaxGhenis
Copy link

Only people with write access to a repo can push a PR from it without using a fork, since it involves creating a branch from the main repo (rather than a branch from one's fork).

@martinholmer
Copy link
Collaborator Author

martinholmer commented May 5, 2024

@MaxGhenis said in issue #56:

Only people with write access to a repo can push a PR from it without using a fork, since it involves creating a branch from the main repo (rather than a branch from one's fork).

OK. What steps do I need to take to get rid of https://github.com/martinholmer/tax-microdata-benchmarking before cloning https://github.com/PSLmodels/tax-microdata-benchmarking on my computer?

@MaxGhenis
Copy link

MaxGhenis commented May 5, 2024

You could do something like the reverse of this: https://stackoverflow.com/a/33817239/1840471

Or simpler could be just creating a new folder on your computer and cloning into there. You don't need to remove the clone of your fork.

@martinholmer
Copy link
Collaborator Author

martinholmer commented May 7, 2024

@nikhilwoodruff and @MaxGhenis,
Following Max's suggestion, I cloned this PSLmodels GitHub repository directly to my computer. Then I created PR #75 containing a one-word change to the README.md file. But the tests on GitHub still failed. Here is the error that caused the test failure:

========================= short test summary info ==========================
FAILED tests/test_flat_file.py::test_2021_flat_file_builds - 
ValueError: Invalid response code 401 for url 

https://api.github.com/repos/policyengine/policyengine-us/
   releases/tags/enhanced-cps-2022

What did I do wrong?

@martinholmer
Copy link
Collaborator Author

Worked after TOKEN was undated on GitHub.
@MaxGhenis and @nikhilwoodruff, Thanks for the help on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants