Skip to content
This repository was archived by the owner on Mar 21, 2024. It is now read-only.

Conversation

@ant0nsc
Copy link
Contributor

@ant0nsc ant0nsc commented Jan 24, 2022

AzureML jobs from failed previous PR builds do not get cancelled, consuming excessive resources.

Please follow the guidelines for PRs contained here. Checklist:

  • Ensure that your PR is small, and implements one change.
  • Add unit tests for all functions that you introduced or modified.
  • Run PyCharm's code cleanup tools on your Python files.
  • Link the correct GitHub issue for tracking.
  • Update the Changelog file: Describe your change in terms of
    Added/Changed/Removed/... in the "Upcoming" section.
  • When merging your PR, replace the default merge message with a description of your PR,
    and if needed a motivation why that change was required.

@ant0nsc ant0nsc enabled auto-merge (squash) January 24, 2022 16:37
@ant0nsc ant0nsc linked an issue Jan 24, 2022 that may be closed by this pull request
@ant0nsc ant0nsc merged commit 61d9cab into main Jan 25, 2022
@ant0nsc ant0nsc deleted the antonsc/cancel_jobs branch January 25, 2022 09:07
javier-alvarez pushed a commit that referenced this pull request Feb 1, 2022
AzureML jobs from failed previous PR builds do not get cancelled, consuming excessive resources. Now kill all queued and running jobs before starting new ones.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Avoid AzureML job queuing in PR jobs

4 participants