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

Regression test coverage for AzureML runs #492

Merged
merged 16 commits into from
Jun 17, 2021
Merged

Conversation

ant0nsc
Copy link
Contributor

@ant0nsc ant0nsc commented Jun 15, 2021

Adding the capability for any run in AzureML to compare its results against a set of baseline results.

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 linked an issue Jun 15, 2021 that may be closed by this pull request
@ant0nsc ant0nsc enabled auto-merge (squash) June 16, 2021 14:07
@ant0nsc ant0nsc merged commit 01c31ed into main Jun 17, 2021
@ant0nsc ant0nsc deleted the antonsc/regressiontests branch June 17, 2021 20:37
@ant0nsc ant0nsc mentioned this pull request Jun 18, 2021
6 tasks
ant0nsc added a commit that referenced this pull request Jun 21, 2021
- The regresssion test code in #492 missed out files in AzureML, because the wrong function was called in the main workflow.
- Cleaner folder structure for regression test results
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.

Enable a more detailed regression check for model training
5 participants