triage anaconda upload failure #2150
Conversation
ndgrigorian
commented
Sep 15, 2025
ndgrigorian
commented
- Have you provided a meaningful PR description?
- Have you added a test, reproducer or referred to an issue with a reproducer?
- Have you tested your changes locally for CPU and GPU devices?
- Have you made sure that new changes do not introduce compiler warnings?
- Have you checked performance impact of proposed changes?
- Have you added documentation for your changes, if necessary?
- Have you added your changes to the changelog?
- If this PR is a work in progress, are you opening the PR as a draft?
|
Deleted rendered PR docs from intelpython.github.com/dpctl, latest should be updated shortly. 🤞 |
|
Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_125 ran successfully. |
|
Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_126 ran successfully. |
|
Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_127 ran successfully. |
|
Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_128 ran successfully. |
ndgrigorian
force-pushed
the
triage-conda-upload-failure
branch
from
032f040 to
756d215
Compare
|
Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_129 ran successfully. |
|
Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_128 ran successfully. |
ndgrigorian
force-pushed
the
triage-conda-upload-failure
branch
from
756d215 to
6905f01
Compare
|
Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_128 ran successfully. |
|
the issue seems to have been connected to an issue between anaconda-client and anaconda-auth, but it remains unknown why this only surfaced when the token was regenerated (caching somewhere?) either way, this is a successful POC for a fix in a separate PR |
2 participants
