-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Validate fp16 dynamic loss scaling parameters are positive #8050
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
Merged
tohtana
merged 4 commits into
deepspeedai:master
from
aryanputta:validate-fp16-dynamic-loss-scale
Jun 22, 2026
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
68eae02
Validate fp16 dynamic loss scaling parameters are positive
aryanputta 27af879
Gate fp16 dynamic-scale validation on dynamic loss scaling
aryanputta 427695f
Reject bool and non-finite values for fp16 dynamic-scale params
aryanputta 3440b8b
Merge branch 'master' into validate-fp16-dynamic-loss-scale
tohtana File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,31 @@ | ||
| # Copyright (c) Microsoft Corporation. | ||
| # SPDX-License-Identifier: Apache-2.0 | ||
|
|
||
| # DeepSpeed Team | ||
|
|
||
| import pytest | ||
| from pydantic import ValidationError | ||
|
|
||
| from deepspeed.runtime.precision_config import DeepSpeedFP16Config | ||
|
|
||
|
|
||
| @pytest.mark.parametrize("field", ["loss_scale_window", "min_loss_scale"]) | ||
| @pytest.mark.parametrize("value", [0, -1, float("inf"), float("nan"), True]) | ||
| def test_fp16_dynamic_scale_rejects_invalid_values(field, value): | ||
| with pytest.raises(ValidationError): | ||
| DeepSpeedFP16Config(**{field: value}) | ||
|
|
||
|
|
||
| @pytest.mark.parametrize("field", ["loss_scale_window", "min_loss_scale"]) | ||
| @pytest.mark.parametrize("value", [1, 1000, "2"]) | ||
| def test_fp16_dynamic_scale_accepts_valid_values(field, value): | ||
| cfg = DeepSpeedFP16Config(**{field: value}) | ||
| assert getattr(cfg, field) > 0 | ||
|
|
||
|
|
||
| @pytest.mark.parametrize("field", ["loss_scale_window", "min_loss_scale"]) | ||
| @pytest.mark.parametrize("value", [[], {}]) | ||
| def test_fp16_dynamic_scale_invalid_type_has_clear_error(field, value): | ||
| with pytest.raises(ValidationError) as excinfo: | ||
| DeepSpeedFP16Config(**{field: value}) | ||
| assert "must be a number" in str(excinfo.value) |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This rejects existing static-loss-scale configs that happen to carry
loss_scale_windowormin_loss_scalevalues such as0, even though those fields are only used when dynamic loss scaling is enabled. I checkedDeepSpeedEngine.dynamic_loss_scale()indeepspeed/runtime/engine.py, which returns true only whenfp16.loss_scale == 0; withloss_scale > 0the optimizer uses the static scale and these dynamic parameters are ignored, so failing config construction here is a compatibility regression for otherwise valid static fp16 setups.Useful? React with 👍 / 👎.