Skip to content

Add py3.13 CI linux-jammy-py3_13-gcc11-build and test#143087

Closed
atalman wants to merge 2 commits into
pytorch:mainfrom
atalman:py313_ci_jammy
Closed

Add py3.13 CI linux-jammy-py3_13-gcc11-build and test#143087
atalman wants to merge 2 commits into
pytorch:mainfrom
atalman:py313_ci_jammy

Conversation

@atalman

@atalman atalman commented Dec 12, 2024

Copy link
Copy Markdown
Collaborator

Add py3.13 CI linux-jammy-py3_13-gcc11-build and test - Same build and test as existing py3_9

@atalman atalman requested a review from a team as a code owner December 12, 2024 01:30
@pytorch-bot pytorch-bot Bot added the topic: not user facing topic category label Dec 12, 2024
@pytorch-bot

pytorch-bot Bot commented Dec 12, 2024

Copy link
Copy Markdown

🔗 Helpful Links

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

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

❌ 3 New Failures

As of commit 17d977e with merge base 06075d3 (image):

NEW FAILURES - The following jobs have failed:

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

@huydhn huydhn left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think we need one for 3.13t?

@atalman

atalman commented Dec 12, 2024

Copy link
Copy Markdown
Collaborator Author

Hi @huydhn yes we should probably add for 3.13t as well. Also for this PR I believe more work is needed, I see failures here: #142870

@seemethere

Copy link
Copy Markdown
Member

Hi @huydhn yes we should probably add for 3.13t as well. Also for this PR I believe more work is needed, I see failures here: #142870

When we do this it should probably be a different workflow and be activated with ciflow / on push to main.

@github-actions

Copy link
Copy Markdown
Contributor

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

@github-actions github-actions Bot added the Stale label Feb 10, 2025
@github-actions github-actions Bot closed this Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants