-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
automl: explictly update timeoutes due to default library changes #2719
Conversation
automl/cloud-client/src/main/java/com/example/automl/ImportDataset.java
Outdated
Show resolved
Hide resolved
automl/cloud-client/src/main/java/com/example/automl/ImportDataset.java
Outdated
Show resolved
Hide resolved
Your PR has attempted to merge for 3 hours. Please check that all required checks have passed, you have an automerge label, and that all your reviewers have approved the PR |
AutoML provides no guarantee on how long this could take and normally would send an email followup. Though normally, I see this finish in under 10 mins. Trying to pin down if TASK CANCELLED is actually related to a timeout or not.
Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, or one of your required reviews was not approved. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot. |
…anges (#2719) * automl: explictly update timeoutes due to library changes in the defaults * Update ImportDataset.java * try bumping timeout AutoML provides no guarantee on how long this could take and normally would send an email followup. Though normally, I see this finish in under 10 mins. Trying to pin down if TASK CANCELLED is actually related to a timeout or not. * update timeouts for all import methods * undo changes to TablesImport, add catch for Cancellation Exception * update to correct CancelledException * wrong cancellation again * run tests * log to error * test * reset changes that printed error * set retry settings * add timeout check to beta code
…anges (#2719) * automl: explictly update timeoutes due to library changes in the defaults * Update ImportDataset.java * try bumping timeout AutoML provides no guarantee on how long this could take and normally would send an email followup. Though normally, I see this finish in under 10 mins. Trying to pin down if TASK CANCELLED is actually related to a timeout or not. * update timeouts for all import methods * undo changes to TablesImport, add catch for Cancellation Exception * update to correct CancelledException * wrong cancellation again * run tests * log to error * test * reset changes that printed error * set retry settings * add timeout check to beta code
…anges (#2719) * automl: explictly update timeoutes due to library changes in the defaults * Update ImportDataset.java * try bumping timeout AutoML provides no guarantee on how long this could take and normally would send an email followup. Though normally, I see this finish in under 10 mins. Trying to pin down if TASK CANCELLED is actually related to a timeout or not. * update timeouts for all import methods * undo changes to TablesImport, add catch for Cancellation Exception * update to correct CancelledException * wrong cancellation again * run tests * log to error * test * reset changes that printed error * set retry settings * add timeout check to beta code
Fixes PR: #2704
pom.xml
parent set to latestshared-configuration
mvn -P lint clean verify
)Checkstyle
passing is required;Spotbugs
,ErrorProne
,PMD
, etc.ERROR
's are advisory only)