-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Open
Labels
api: batchIssues related to the Batch API.Issues related to the Batch API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.samplesIssues that are directly related to samples.Issues that are directly related to samples.triage meI really want to be triaged.I really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Description
The integration tests for the Batch samples were disabled in #9841.
Reason:
The samples clean up logic requires regular polling of each Job created in the test file. Jobs can take ~2-4 minutes to complete. The polling logic allows for regular retries up until 1200 seconds before erroring out. Unfortunately, not all of the jobs are marked as SUCCEEDED or FAILED in the time provided.
The Batch API has a CancelJob
method that is available in v1alpha but not v1. Once this method is available to the v1 channel, we should be able to cancel a job after it has been created and then delete it.
Metadata
Metadata
Assignees
Labels
api: batchIssues related to the Batch API.Issues related to the Batch API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.samplesIssues that are directly related to samples.Issues that are directly related to samples.triage meI really want to be triaged.I really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.