| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
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 |
Sorry, something went wrong.
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. |
Sorry, something went wrong.
…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
| Back | FazBrowse Home | New Git URL |
Fixes PR: #2704