Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

nightly timeout: cpu-torch-multi-latest multi-rank suite exceeded its time budget

Open
#8,834 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, python, pytorch
Domain
ci-cd, testing-qa

Research direction

Start from the nightly run linked in the issue and read the cpu-torch-multi-latest job log to see which phase hit the 120m or 25m budget. Find the GitHub Actions workflow that defines this job and its timeout settings, then compare them with how long the multi-rank tests take. Done means either a justified budget change or a split suite, and the nightly job finishing within its limit. Raising budgets versus splitting is a maintainer decision, so confirm it in the thread first.

Written by the indexing model from the issue text.

Description

nightly-triage

The nightly multi-rank CPU run died at its time budget (class: timeout) at 64915cb41bfe12830c618856cb95186799be0099.
The multi-rank suite likely outgrew its 120m/25m phase budgets; consider raising them or splitting the suite. Run: https://github.com/deepspeedai/DeepSpeed/actions/runs/38849719748

Dominant language
Python
Stars
43.3k
Forks
5.1k
Avg merge
4d 21h
Merged PRs (30d)
66

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from deepspeedai/DeepSpeed

All issues in deepspeedai/DeepSpeed

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.