-
Notifications
You must be signed in to change notification settings - Fork 11
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
Pass R errors through to Conbench #143
Conversation
logging.exception(json.dumps(error)) | ||
return error, output | ||
result["error"]["command"] = r_command | ||
logging.exception(f"Errored result (not posted): {json.dumps(result)}") |
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.
Theoretically we could post these to Conbench now, but I'm not sure whether there's value in doing so. Errors within the benchmark won't hit this—this is for when things bomb out entirely somehow, e.g. you spelled the name of the benchmark wrong.
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.
A lot of this is just rearranging; I moved the single-use assert_*
function bodies directly into the tests so you can see what they're testing without navigating all over the code.
assert output is None | ||
@pytest.mark.parametrize("error_type", ["NULL"]) | ||
@pytest.mark.parametrize("output_type", ["NULL", "'warning'"]) | ||
def test_r_only_placebo(error_type, output_type): |
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.
this is new
|
||
@pytest.mark.parametrize("error_type", ["'base'"]) | ||
@pytest.mark.parametrize("output_type", ["NULL", "'warning'"]) | ||
def test_r_only_exception(error_type: str, output_type: str): |
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.
This is a significant refactor of an outdated test which no longer raised errors like before because arrowbench handles them properly. Now this tests that labs/benchmarks handles errors arrowbench catches properly.
Pull Request Test Coverage Report for Build 5340132227
💛 - Coveralls |
The changes here are relatively simple and well-tested, so I'm going to merge this, but post-merge reviews are welcome; happy to do a follow-up is necessary. I'll keep an eye on buildkite to see if anything goes awry. |
Closes #134. Builds on voltrondata-labs/arrowbench#138 to take results with an
error
element and pass it through to Conbench properly. Improves some tests along the way.Tests are passing locally, but I want to run this against a local Conbench instance to make sure nothing is malformed before merging.