Conversation
bhimrazy
requested review from
k223kim,
lianakoleva and
tejapulagam
as code owners
September 24, 2026 13:31
bhimrazy
added this pull request to stack #2849
September 24, 2026 13:31
On torch nightly, test_core_vs_torch_consistency_cross_entropy with nvFuser takes 175-240s per dtype, and float16 keeps landing on the ops job's 240s limit: 240.18s call ...cross_entropy_nvfuser_cuda_thunder.dtypes.float16 Failed: Timeout (>240.0s) from pytest-timeout. It is the slowest test in test_ops by a wide margin (the next is ~90s), so raise the limit for it alone rather than for the whole job.
bhimrazy
force-pushed
the
bhimrazy/cross-entropy-nvfuser-timeout
branch
from
September 24, 2026 13:44
7e77f46 to
dd9f837
Compare
lianakoleva
approved these changes
Sep 24, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What does this PR do?
Gives the nvFuser
cross_entropyconsistency test a 360s timeout (pytest.mark.timeoutthrough its opinfo), instead of raising the limit for the whole ops job.Problem: on torch nightly,
test_core_vs_torch_consistency_cross_entropy_nvfuser_cudatakes 175–240s per dtype, and float16 keeps landing on the ops job's 240s limit. It is the slowest test intest_opsby far; the next one takes about 90s.Related CI:
all-tests.yamlopsonpt_main-dev:test_core_vs_torch_consistency_cross_entropy_nvfuser_cuda_thunder.dtypes.float16.CI log (
ops,pt_main-dev, on #2847)Part 13 of the breakdown of #2832.