Skip to content

fix broken usafacts tests to read from the proper directories #314

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

Merged
merged 179 commits into from
Oct 20, 2020

Conversation

sgsmob
Copy link
Contributor

@sgsmob sgsmob commented Oct 15, 2020

usafacts was trying to read/write to/from receiving when run in the tests directory rather than ../receiving. The tests now pass.

korlaxxalrok and others added 30 commits August 5, 2020 15:39
…hi#182)

* update cache

* remove default end_date

* update start_date

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cache

* update cahce

* Set up initial google_health-deploy branch

- Add new google_health Jenkins pipeline stage scripts
- Add the abilty for Ansible to write either a file or a template
  depending on which has been configured for the indicator
- Add Ansible template directory (special tall bookshelf)
- Add the ability to keep sensitive variables in `vault.yaml`
- Add google_health production params template

Encrypt vault.yaml

* Use templates dir

* Remove end date from params

* Switch to midas export dir

* Properly rename Jenkins pipeline stage scripts

* Handle google_health's testing needs
- Add: Ansible playbook for securely handling placing the
  `params.json` template we need for testing. This will happen during
  the Jenkins build stage when we are setting up the venv in the
  workspace on the Jenkins server.
- Add: Test `params.json` template.
- Add: Jenkins user variable.
- Fix: Was incorrectly trying to use a file instead of a template in
  `ansible-deploy.yaml`.
- Add: Call the small Ansible playbook from the Jenkins build wrapper.

* Change to the Ansible root dir before trying to do Ansible things

* Delegate to localhost

* Tell Ansible we want to connect locally for this playbook

* Remove set -x from Bash scripts

* Add initial Jenkins/Ansible necessities for CI/CD
and Automation
- Add Jenkins pipeline scripts
- Add production params template
- Update vars and vault files with AWS secrets

* Remove ght cache files

* Disable pylint convention messages

* Work around linter errors

Co-authored-by: Addison Hu <[email protected]>
Co-authored-by: Jingjing Tang <[email protected]>
Merge main into deploy-google_health
@jingjtang
Copy link
Contributor

Hi @sgsmob, I think a better way to solve this is to add a ./receiving folder under tests, then we will stored the output from tests under usafacts/tests/receiving and check those file there.

The current solution seems weird. Since the receiving dir in usafacts/tests/params.json is stilled defined as usafacts/tests/receiving, but in test_run.py we check the output from usafacts/receiving.

@sgsmob
Copy link
Contributor Author

sgsmob commented Oct 19, 2020

Changed to add the ./receiving directory.

jingjtang
jingjtang previously approved these changes Oct 19, 2020
Copy link
Contributor

@jingjtang jingjtang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All unit tests passed

@krivard krivard changed the base branch from main to deploy-usafacts October 20, 2020 13:44
@krivard krivard dismissed jingjtang’s stale review October 20, 2020 13:44

The base branch was changed.

krivard
krivard previously approved these changes Oct 20, 2020
@krivard
Copy link
Contributor

krivard commented Oct 20, 2020

Oh ffs. @korlaxxalrok this PR seems to trigger the same pylint/asteroid "recursion limit exceeded" problem as we were having in JHU. Tests seem to pass in Jingjing's environment so I think we're okay to disable them here the same way. If you agree, go ahead and do that so we can unblock Mike.

Afterwards, could you work with @benjaminysmith to figure out a more permanent solution?

@sgsmob
Copy link
Contributor Author

sgsmob commented Oct 20, 2020

Yes I observed the recursion limit issue. FWIW I have a pylint extension on my IDE and I corrected the mistakes there.

@korlaxxalrok
Copy link
Contributor

I'll disable linting for now, and then spend some time looking at an actual fix.

@korlaxxalrok
Copy link
Contributor

@krivard @sgsmob Linting is disabled.

@krivard krivard merged commit b0bb289 into cmu-delphi:deploy-usafacts Oct 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.