-
Notifications
You must be signed in to change notification settings - Fork 1.2k
fix: Remove confusing log line emitted during feature group ingestion #3597
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
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.
/bot run all
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
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.
/bot run notebook-tests, slow-tests, pr
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Just had a quick look at the failure logs. Notebook tests
Slow tests
sagemaker-python-sdk-pr
I see one failure related to feature store (first two failures look unrelated) but the failing test is exercising a path that is unmodified in this CR. Build logs also show
Perhaps we should increase the limit or delete some old feature groups ? |
@psnilesh Yes first two are flaky tests we are dealing with; I'll look into if we need feature grouplimit increase, will let you know |
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.
/bot run slow-tests
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
@claytonparnell is this PR waiting on something, like a fix for those transient failures ? |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
…aws#3597) Co-authored-by: Nilesh PS <[email protected]>
…aws#3597) Co-authored-by: Nilesh PS <[email protected]>
Description
A feature store worker that's been told to ingest rows 1 to 100 of a data frame would emit a log line given below if some rows failed to ingest,
This often confuse some customers into thinking more rows have failed than what actually have, because the same line is logged if all but one row had succeeded .
There is already a log line in line 234 indicating row number and exception of failed rows that customers can use to debug. This PR is for removing aforementioned extra log line.
Testing
Verified the change by installing SDK locally and ingesting a data frame containing some faulty rows.
Merge Checklist
General
Tests
This is a only a minor logging change, so below checklist is not applicable. The code path is already covered by existing unit and integration tests.
unique_name_from_base
to create resource names in integ tests (if appropriate)By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.