Skip to content

Do not count STOPPED as a model fitting failure #2767

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

Closed
wants to merge 1 commit into from

Conversation

saitcakmak
Copy link
Contributor

Summary:
Discovered this while debugging a CUDA test failure. I don't know why this was only raised when running on GPU but it was failing model fitting with status STOPPED (maybe it was slower and somehow timed out in scipy_minimize?).

Either way, we shouldn't count termination due to user specified criterion as a model fitting failure.

Differential Revision: D70994718

@facebook-github-bot facebook-github-bot added the CLA Signed Do not delete this pull request or issue due to inactivity. label Mar 11, 2025
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D70994718

Copy link

codecov bot commented Mar 11, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.99%. Comparing base (307cf04) to head (b0b9473).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2767   +/-   ##
=======================================
  Coverage   99.99%   99.99%           
=======================================
  Files         203      203           
  Lines       18705    18705           
=======================================
  Hits        18704    18704           
  Misses          1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Summary:

Discovered this while debugging a CUDA test failure. I don't know why this was only raised when running on GPU but it was failing model fitting with status `STOPPED` (maybe it was slower and somehow timed out in `scipy_minimize`?).

Either way, we shouldn't count termination due to user specified criterion as a model fitting failure.

Reviewed By: Balandat

Differential Revision: D70994718
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D70994718

@facebook-github-bot
Copy link
Contributor

This pull request has been merged in f692836.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed Do not delete this pull request or issue due to inactivity. fb-exported Merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants