-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[AWS SageMaker] Integ test to check CloudWatch logs print feature #4056
Conversation
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.
So this integration test just checks to make sure that we didn't see an error in the logs? We also need to test to ensure that we DID see the correct stdout in the logging.
components/aws/sagemaker/tests/integration_tests/component_tests/test_train_component.py
Outdated
Show resolved
Hide resolved
components/aws/sagemaker/tests/integration_tests/component_tests/test_train_component.py
Outdated
Show resolved
Hide resolved
...ents/aws/sagemaker/tests/integration_tests/component_tests/test_batch_transform_component.py
Outdated
Show resolved
Hide resolved
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.
So this integration test just checks to make sure that we didn't see an error in the logs? We also need to test to ensure that we DID see the correct stdout in the logging.
this is being tested in the Unit tests that all logs are printed
...ents/aws/sagemaker/tests/integration_tests/component_tests/test_batch_transform_component.py
Outdated
Show resolved
Hide resolved
output = utils.run_command( | ||
f"argo logs {workflow_name} -n {utils.get_kfp_namespace()}" | ||
) | ||
output = get_workflow_logs(workflow_name) |
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.
nit: Ideally there should be some error handling here if workflow name is not found, but I guess argo will take care of the right error.
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.
What is the response to get_workflow_logs
if there is a bad input? I imagine it would be a garbled error message that we are then using as the name.
...ents/aws/sagemaker/tests/integration_tests/component_tests/test_batch_transform_component.py
Outdated
Show resolved
Hide resolved
...ents/aws/sagemaker/tests/integration_tests/component_tests/test_batch_transform_component.py
Outdated
Show resolved
Hide resolved
...ents/aws/sagemaker/tests/integration_tests/component_tests/test_batch_transform_component.py
Outdated
Show resolved
Hide resolved
components/aws/sagemaker/tests/integration_tests/component_tests/test_train_component.py
Outdated
Show resolved
Hide resolved
output = utils.run_command( | ||
f"argo logs {workflow_name} -n {utils.get_kfp_namespace()}" | ||
) | ||
output = get_workflow_logs(workflow_name) |
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.
What is the response to get_workflow_logs
if there is a bad input? I imagine it would be a garbled error message that we are then using as the name.
cc38dd6
to
a359c55
Compare
d589f48
to
0ddf3db
Compare
0ddf3db
to
898f1f2
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: RedbackThomson The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…beflow#4056) * Integ test for cw logs * Update license file version to 0.5.3 * update version in yaml * add changelog
Integration test checks if there is any error in fetching logs