-
Notifications
You must be signed in to change notification settings - Fork 1
Rewrite cassettes retry #170
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
Conversation
…settes from failed/succeeded tests
@sckott -- I like this addition, should make debugging much easier, but I'm a little confused where to look for the list of passed/failed test. I went to the GitHub Action linked above and the "List all cassettes passed" function just says "Array", same with failed cassettes. Am I looking in the wrong place? |
@tefirman yeah I need to fix that. Its printing the class of the array of tests that failed or succeeded rather than the actual list |
Waiting on fix to the test user from Dan |
@tefirman okay, we're unblocked now by fix to test user, but the failed and succeeded tests are still not showing up correctly ... |
…predefined paths to include in PR; only run one test file for quick check
Okay, @tefirman and @seankross can you take another look please - see last run https://github.com/FredHutch/wdl-unit-tests/actions/runs/14979902855 We're now doing the following approach:
With the current state of this action I haven't seen how it behaves when tests fail yet, but I'm pretty sure it will work well. |
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.
Thank you so much Scott, it looks clean but I can smell how this went through several painful iterations. I think this is right on the money though.
- name: Run tests and process changes | ||
id: process-changes | ||
run: | | ||
make test_api_rewrite_json_report || true |
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.
Love the elegance of make [command] || true
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.
yeah, there's many ways to achieve this but this one seems good
thanks @seankross |
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.
Looks awesome, really like the clear call-out of failing tests. Thanks for putting this together, @sckott !
thanks. @tefirman |
fix #168
definitely squash and merge - lots of iterating to fix actions commits
Here's a run of this new workflow: https://github.com/FredHutch/wdl-unit-tests/actions/runs/14801625090/job/41732524382
Here's the generated PR from the above workflow run: #169
Changes here:
pytest
pluginpytest-json-report
pytest_json_modifyreport
that when the--json-report
flag is used withpytest
a report of test results is written to a json file. this fixture is not used when the--json-report
flag is absent via this line@pytest.hookimpl(optionalhook=True)
test_api_rewrite_json_report
to do cassette rewrites AND generate a json reportexit 0
(otherwise any failures would not let us proceed)¿Bueno?