Skip to content

Conversation

@jeanschmidt
Copy link
Contributor

@jeanschmidt jeanschmidt commented Mar 22, 2024

title says it all...

@jeanschmidt jeanschmidt requested a review from a team as a code owner March 22, 2024 16:39
@pytorch-bot
Copy link

pytorch-bot bot commented Mar 22, 2024

🔗 Helpful Links

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

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

✅ You can merge normally! (1 Unrelated Failure)

As of commit 9a1fd7e with merge base 5e66bf5 (image):

FLAKY - The following job failed but was likely due to flakiness present on trunk:

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

@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Mar 22, 2024
@jeanschmidt jeanschmidt changed the title Switch pull job linux-jammy-py3_8-gcc11-build to use ARC with runner groups [CI] Switch pull job linux-jammy-py3_8-gcc11-build to use ARC with runner groups Mar 22, 2024
@jeanschmidt
Copy link
Contributor Author

@pytorchbot rebase

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

@pytorchmergebot
Copy link
Collaborator

Successfully rebased jeanschmidt/switch_to_arc_jammy_38_build onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout jeanschmidt/switch_to_arc_jammy_38_build && git pull --rebase)

@jeanschmidt
Copy link
Contributor Author

@pytorchbot rebase

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

@pytorchmergebot
Copy link
Collaborator

Successfully rebased jeanschmidt/switch_to_arc_jammy_38_build onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout jeanschmidt/switch_to_arc_jammy_38_build && git pull --rebase)

@pytorchmergebot pytorchmergebot force-pushed the jeanschmidt/switch_to_arc_jammy_38_build branch from c599c89 to 9a1fd7e Compare March 26, 2024 10:02
@jeanschmidt
Copy link
Contributor Author

@pytorchbot merge -f "Relevant jobs linux-jammy-py3_8-gcc11-build and dependencies are successful"

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

malfet added a commit that referenced this pull request Mar 26, 2024
`CXX_AVX[2|512]_FOUND` flags should indicate whether compiler supports generating code  for given instruction set, rather than whether host machine can run the generated code.

This fixes a weird problem that surfaced after #122503 when builder can sometimes be dispatched to an old CPU architecture, that can not run AVX512 instructions, but can compile for those just fine
pytorchmergebot pushed a commit that referenced this pull request Mar 26, 2024
`CXX_AVX[2|512]_FOUND` flags should indicate whether compiler supports generating code  for given instruction set, rather than whether host machine can run the generated code.

This fixes a weird problem that surfaced after #122503 when builder can sometimes be dispatched to an old CPU architecture, that can not run AVX512 instructions, but can compile for those just fine

Pull Request resolved: #122708
Approved by: https://github.com/jeanschmidt
pytorch-bot bot pushed a commit that referenced this pull request Apr 22, 2024
`CXX_AVX[2|512]_FOUND` flags should indicate whether compiler supports generating code  for given instruction set, rather than whether host machine can run the generated code.

This fixes a weird problem that surfaced after #122503 when builder can sometimes be dispatched to an old CPU architecture, that can not run AVX512 instructions, but can compile for those just fine

Pull Request resolved: #122708
Approved by: https://github.com/jeanschmidt
@github-actions github-actions bot deleted the jeanschmidt/switch_to_arc_jammy_38_build branch April 26, 2024 01:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants