Skip to content

Conversation

r-barnes
Copy link
Contributor

@r-barnes r-barnes commented Mar 17, 2025

Summary:
-Wunused-exception-parameter has identified an unused exception parameter. This diff removes it.

This:

try {
    ...
} catch (exception& e) {
    // no use of e
}

should instead be written as

} catch (exception&) {

If the code compiles, this is safe to land.

Test Plan: Sandcastle

Reviewed By: dtolnay

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel

Copy link

pytorch-bot bot commented Mar 17, 2025

🔗 Helpful Links

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

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

⏳ No Failures, 45 Pending

As of commit 1a30fa9 with merge base 224cd9f (image):
💚 Looks good so far! There are no failures yet. 💚

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

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

@facebook-github-bot facebook-github-bot added the oncall: jit Add this issue/PR to JIT oncall triage queue label Mar 17, 2025
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D71290929

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Mar 17, 2025
@Skylion007
Copy link
Collaborator

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: This PR has internal changes and must be landed via Phabricator! Please try reimporting/rexporting the PR!

Details for Dev Infra team Raised by workflow job

@r-barnes r-barnes added release notes: cpp release notes category topic: improvements topic category labels Mar 17, 2025
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D71290929

…/src/ATen/cuda/CUDABlas.cpp (pytorch#149328)

Summary:
Pull Request resolved: pytorch#149328

`-Wunused-exception-parameter` has identified an unused exception parameter. This diff removes it.

This:
```
try {
    ...
} catch (exception& e) {
    // no use of e
}
```
should instead be written as
```
} catch (exception&) {
```

If the code compiles, this is safe to land.

Test Plan: Sandcastle

Reviewed By: dtolnay

Differential Revision: D71290929
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D71290929

@r-barnes
Copy link
Contributor Author

@pytorchbot merge -f "Good to go"

@pytorchmergebot
Copy link
Collaborator

Can't merge closed PR #149328

@izaitsevfb izaitsevfb reopened this Mar 19, 2025
@izaitsevfb
Copy link
Contributor

@pytorchbot merge -f "Good to go"

@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

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

Labels

ciflow/trunk Trigger trunk jobs on your pull request fb-exported Merged oncall: jit Add this issue/PR to JIT oncall triage queue release notes: cpp release notes category topic: improvements topic category topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants