Repository navigation
build(deps): bump setuptools from 82.0.1 to 83.0.0 in /projects/hipblaslt/tensilelite - #9651
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [setuptools](https://github.com/pypa/setuptools) from 82.0.1 to 83.0.0. - [Release notes](https://github.com/pypa/setuptools/releases) - [Changelog](https://github.com/pypa/setuptools/blob/main/NEWS.rst) - [Commits](pypa/setuptools@v82.0.1...v83.0.0) --- updated-dependencies: - dependency-name: setuptools dependency-version: 83.0.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
github-actions
Bot
added
project: hipblaslt
project: hipsparselt
ci:hipsparselt-fast
labels
❌ PR Check — Action Required
📖 Need help? See the Policy FAQ for details on every check and how to fix failures. |
|
🚫 Please fix the failed policies before requesting reviews. The following policy checks failed:
The |
assistant-librarian
Bot
added
the
external contribution
Codecov Report✅ All modified and coverable lines are covered by tests. ❌ Your project check has failed because the head coverage (76.84%) is below the target coverage (80.00%). You can increase the head coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## develop #9651 +/- ##
========================================
Coverage 64.22% 64.22%
========================================
Files 2763 2763
Lines 450264 450264
Branches 66249 66249
========================================
Hits 289142 289142
Misses 140243 140243
Partials 20879 20879
*This pull request uses carry forward flags. Click here to find out more. 🚀 New features to boost your workflow:
|
Contributor
|
This pull request has been inactive for 25 days and will be marked as stale. If you would like to keep this PR open, please:
This PR will be automatically closed in 5 days if no further activity occurs. |
Contributor
|
This pull request has been automatically closed due to inactivity (30 days with no updates). If you'd like to continue working on this, feel free to reopen the PR or create a new one. |
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/uv/projects/hipblaslt/tensilelite/setuptools-83.0.0
branch
August 23, 2026 00:23
Merged
4 of 7 tasks
aalabsi-amd
added a commit
that referenced
this pull request
Nov 2, 2026
… and Windows gfx1151 Quarantine the MIOpen failures seen on TheRock bump PRs #9651/#9680 (issue #14874) after #13107 widened the TheRock tiers: - gfx120X: GPU_ConvAIModelLoad_FP32* (no bundled fdeep models, ALMIOPEN-2966) and Smoke/CPU_DBSync_NONE.StaticFDBSync/11 (no gfx120138 system db on 56-CU gfx1201 hosts, #13416). - Linux gfx120X: GPU_SoftmaxFind20_FP16.softmaxBackward_log_channel_mode_fp16 hangs to the ctest timeout on gfx1201 hosts. - Windows gfx115X: CPU_PerfDb_NONE.{RamDb,PlainTextDb}_AllTests hang in the multiprocess write phase.
aalabsi-amd
added a commit
that referenced
this pull request
Nov 3, 2026
… and Windows gfx1151 (#14882) JIRA-ID : ROCM-31323 ALMIOPEN-2966, ALMIOPEN-3129, ALMIOPEN-3130 ## Motivation The rocm-libraries bump into TheRock went red with #13107 (ROCm/TheRock#9651, `f4e24d5` → `8c41584`; still red on #9680). #13107 added Jenkins-only gtest families to the TheRock tiers, and TheRock tests gfx120X and Windows gfx1151, which the rocm-libraries PR gate doesn't cover. Tracking issue: #14874. Bump PR #9651 run [41113572856](https://github.com/ROCm/TheRock/actions/runs/41113572856) failed 4 of 4 attempts. #9680 run [41405101044](https://github.com/ROCm/TheRock/actions/runs/41405101044) also failed. Develop nightlies [41179300934](https://github.com/ROCm/rocm-libraries/actions/runs/41179300934) and [41283494663](https://github.com/ROCm/rocm-libraries/actions/runs/41283494663) were read across all attempts too. | # | Failure | Lane | Evidence | Action | |---|---|---|---|---| | 1 | `GPU_ConvAIModelLoad_FP32.BundledFdeepModelsLoad`: `conv_ai_nd_heuristics_test.cpp:962` "no fdeep .tn.model files found" | Linux + Windows gfx120X | 10 of 10 executions on 8 hosts (#9651 attempts 1–4, #9680) | **exclude** on `gfx120X` (ALMIOPEN-2966, already excluded on gfx110X/gfx115X) | | 2 | `GPU_SoftmaxFind20_FP16.softmaxBackward_log_channel_mode_fp16` hangs after "Testing solution functions..." → `miopen_gtest_standard_gfx120X_suite` ***Timeout 3600 s | Linux gfx1201 (CS-RORDMZ-DT87, -DT81) | 3 of 3 executions on Linux gfx1201. Passes in < 1.2 s on Linux gfx1200 and Windows gfx1201 (5 of 5) | **exclude** on `gfx120X_linux` (**ALMIOPEN-3130**). New with #13107 (`GPU_SoftmaxFind20_*`) | | 3 | `Smoke/CPU_DBSync_NONE.StaticFDBSync/11`: "Db file does not exist … gfx120138.HIP.fdb.txt" | Windows gfx120X, CS-RORDMZ-DT84 | 1 of 5 Windows gfx1201 executions. Only `gfx120140` dbs ship; the other hosts pass | **exclude** on `gfx120X` (#13416, same cause as `StaticFDBSync/9` on gfx115X). Existed before #13107 | | 4 | `CPU_PerfDb_NONE.{RamDb,PlainTextDb}_AllTests` hang in the multiprocess read or write phase ("Waiting for test processes...") until the ctest or step timeout | Windows gfx1151 | 6 hangs on 5 hosts since 10-31: nightly 41179300934 (RamDb), nightly 41283494663 (RamDb; PlainTextDb on attempts 1–3), #9680 (PlainTextDb). None in nightlies 40833587284 or 41018314721 | **exclude** on `gfx115X_windows` (**ALMIOPEN-3129**) | | 5 | Windows gfx1151 standard shard 3 ***Timeout 3600 s; `Smoke/GPU_HipGraphExistTest_FP32.HipGraphExist/2` took 596 s (7.5 s elsewhere) | #9680, windows-strix-halo-gpu-rocm-10 | runner-specific slowness on top of #13107's larger standard tier | not excluded: time budget, see below | | 6 | Nightly Windows gfx1151 comprehensive shards hit the 120-min step cap (killed in `Full/GPU_Pooling3d_FP16`, `Full/GPU_BnPeract_FP32`, `Full/GPU_Reduce_FP16`) | nightlies 10-31, 11-01 | passed on rerun | not excluded: time budget, see below | | 7 | Linux gfx110X shard 2 ctest timeout (azure scale-set runner) | #9651 attempt 1 | passed on attempts 2–4 | not excluded: flaky runner (TheRock#3845) | | 8 | gfx90a `CPU_PerfDb_NONE.MultiFileDb_AllTests` "terminate called recursively" | #9651 attempt 1 | passed on attempts 2–4, seen once | not excluded: one-off | | 9 | gfx950 shards 1 and 3: no tests ran, `Unexpected HTTP response: 429` | #9651 attempt 1 | infra | not excluded | ## Technical Details Only `projects/miopen/test/gtest/test_categories.yaml` changes. Each entry has the narrowest arch/OS scope that covers the failures, plus an inline ticket or issue reference: - `exclude_gpu_gfx120X`: changed from the bare `*gfx11_common_patterns` alias to a list that also holds `GPU_ConvAIModelLoad_FP32*` (ALMIOPEN-2966) and `Smoke/CPU_DBSync_NONE.StaticFDBSync/11` (#13416). - New `exclude_gpu_gfx120X_linux`: `GPU_SoftmaxFind20_FP16.softmaxBackward_log_channel_mode_fp16`, exact name (ALMIOPEN-3130). The other five `SoftmaxFind20` cases keep running. It only hangs on gfx1201, but the exclusion covers all Linux gfx120X. TheRock takes the arch from `AMDGPU_FAMILIES` (`gfx120X-all` → `gfx120X`), so gfx1200 and gfx1201 runners share one suite. An `exclude_gpu_gfx1201_*` key would build a suite that no runner selects. - `exclude_gpu_gfx115X_windows`: `CPU_PerfDb_NONE.RamDb_AllTests` and `CPU_PerfDb_NONE.PlainTextDb_AllTests` (ALMIOPEN-3129). These two spawn child processes (`DbMultiProcessReadTest`, `DbMultiProcessTest`). `MultiFileDb_AllTests` doesn't, so it stays. Linux gfx115X already excludes `CPU_PerfDb_NONE.*` (ALMIOPEN-2964). Jenkins gets no `add_gtest_negative_filter` change. It has no gfx120X or Windows stage, and these tests passed there before #13107 moved them into the TheRock tiers. Not addressed here: Windows gfx1151 shard time. After #13107, a standard shard runs about 6,550 cases, up from about 3,700. Windows gfx120X shard 3 takes 32–51 min against the 60-min ctest limit, and slow gfx1151 hosts push it over. Excluding single tests won't fix that. It needs a tier move (for example `Full/GPU_Softmax_*` out of standard, as proposed in #13107) or a timeout or shard change in a separate PR. ## Test Plan - `python3 shared/ctest/parse_test_categories.py test_categories.yaml miopen_gtest …`: rc 0, 25 suites. The generated `miopen_gtest_standard_gfx120X_suite` filter contains the three gfx120X entries on Linux. - `yaml_select.py diff --old git:origin/develop`, using the 40,957 case names from the logs above, per arch/OS (every tier): | GPU / OS | Removed (each tier) | |---|---| | gfx1201 Linux | 3: `ConvAIModelLoad`, `StaticFDBSync/11`, `SoftmaxFind20_FP16…channel_mode_fp16` | | gfx1201 Windows | 2: `ConvAIModelLoad`, `StaticFDBSync/11` | | gfx1151 Windows | 2: `CPU_PerfDb_NONE.{RamDb,PlainTextDb}_AllTests` | | gfx1151 Linux, gfx942 Linux, gfx1100 Windows | 0 | - After merge: the next TheRock bump should be green on gfx120X shards 1 and 3 and Windows gfx1151 shard 2. ## Test Result The selection diff above shows exactly the intended cases removed, with no change on other archs. ## Submission Checklist - [x] Each exclusion is scoped to arch/OS and cites a ticket or issue - [x] YAML parses and the generator returns rc 0 - [x] Jira for the gfx1201 `SoftmaxFind20` hang (ALMIOPEN-3130) and the Windows `PerfDb` multiprocess hang (ALMIOPEN-3129) - [ ] Re-enable each entry when its ticket closes - [ ] Look over the contributing guidelines at https://github.com/ROCm/TheRock/blob/main/GOVERNANCE.md#pull-requests.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps setuptools from 82.0.1 to 83.0.0.
Changelog
Sourced from setuptools's changelog.
Commits
6519f72Bump version: 82.0.1 → 83.0.0d1151b1Merge pull request #5250 from pypa/feature/distutils-d7633fbeda2df31eCapture removal of dry_run parameter in changelog.00144dcMoved newsfragment to the release where it occurred.a4a5a2bAdd news fragment.77470c2Merge https://github.com/pypa/distutils into feature/distutils-d7633fbed3c43897Merge pull request #5247 from pypa/copilot/fix-pypy-version-issuebb6ea66Bump PyPy from 3.10 to 3.11 in CI workflowa2bc3acFix broken intersphinx reference to build's installation docs2d6a739Use stacked parametrize decorators instead of itertools.productDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.