Skip to content

Update requirements.txt#3793

Closed
sekyondaMeta wants to merge 3 commits intomainfrom
updatetosphinx045
Closed

Update requirements.txt#3793
sekyondaMeta wants to merge 3 commits intomainfrom
updatetosphinx045

Conversation

@sekyondaMeta
Copy link
Contributor

@sekyondaMeta sekyondaMeta commented Mar 12, 2026

Updating to sphinxtheme 0.4.5, and adding a banner

@sekyondaMeta
Update requirements.txt
abb1f69 
Updating to sphinxtheme 0.4.5, and adding a banner
@pytorch-bot
Copy link

pytorch-bot bot commented Mar 12, 2026 •
edited
Loading

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/tutorials/3793

Note: Links to docs will display an error until the docs builds have been completed.

❌ 30 New Failures, 1 Pending, 1 Unrelated Failure

As of commit 49af2db with merge base 29580ff (image):

NEW FAILURES - The following jobs have failed:

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla bot added the cla signed label Mar 12, 2026
@sekyondaMeta
Copy link
Contributor Author

sekyondaMeta commented Mar 12, 2026

@claude What is causing the failures on this PR

@claude
Copy link

claude bot commented Mar 12, 2026 •
edited
Loading

Claude finished @sekyondaMeta's task in 1m 14s —— View job

CI Failure Analysis

  • Review PR changes
  • Check CI failure logs
  • Identify root cause
  • Provide summary

Root Cause

The failures are NOT caused by your PR changes (the sphinx theme bump or banner config). All 28 failures stem from a pre-existing pip dependency conflict in the Docker image build step.

The error from the Docker Build log:

ERROR: Cannot install -r ./requirements.txt (line 55) and ray because these
package versions have conflicting dependencies.

The conflict is caused by:
    mosaic 0.1.0 depends on click>=8.3.0
    ray 2.52.1 depends on click!=8.3.* and >=7.0
  • Line 55 of .ci/docker/requirements.txt installs mosaic from git (git+https://github.com/facebookresearch/mosaic.git), which requires click>=8.3.0.
  • ray 2.52.1 (a transitive dependency) requires click!=8.3.* (i.e., anything except 8.3.x) and >=7.0.
  • These constraints are mutually exclusive since click 8.3.x is the only version satisfying >=8.3.0 while simultaneously being blocked by !=8.3.*. If a newer click version (e.g., 8.4+) existed, it would satisfy both, but apparently none is currently available in the build environment.

Since the Docker image build fails, all 15 build worker jobs in both the "Build tutorials" and "Build tutorials (nightly/test)" workflows also fail at the "Calculate/build docker image" step — they depend on this image.

This is a pre-existing issue

The pytorch-bot also flagged shard 11 as a "BROKEN TRUNK" failure (present on the merge base 29580ff), confirming this conflict existed before your PR. Your changes to pytorch_sphinx_theme2==0.4.5 and the announcement_banner config in conf.py are unrelated.

Possible Fix

To unblock CI, someone would need to resolve the click version conflict — likely by pinning click to a version >=8.4 (if one exists) or updating/pinning mosaic or ray to compatible versions.

|

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

cla signed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@sekyondaMeta