Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test publish::invalid_token flake on Windows #8535

Open
zanieb opened this issue Oct 24, 2024 · 1 comment
Open

Test publish::invalid_token flake on Windows #8535

zanieb opened this issue Oct 24, 2024 · 1 comment
Labels
internal A refactor or improvement that is not user-facing

Comments

@zanieb
Copy link
Member

zanieb commented Oct 24, 2024

running 1 test
test publish::invalid_token has been running for over 60 seconds
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Snapshot Summary ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Snapshot: invalid_token
Source: E:\uv:33
───────────────────────────────────────────────────────────────────────────────
Expression: snapshot
───────────────────────────────────────────────────────────────────────────────
-old snapshot
+new results
────────────┬──────────────────────────────────────────────────────────────────
    5     5 │ warning: `uv publish` is experimental and may change without warning
    6     6 │ Publishing 1 file to https://test.pypi.org/legacy/
    7     7 │ Uploading ok-1.0.0-py3-none-any.whl ([SIZE])
    8     8 │ error: Failed to publish `../../scripts/links/ok-1.0.0-py3-none-any.whl` to https://test.pypi.org/legacy/
    9       │-  Caused by: Permission denied (status code 403 Forbidden): 403 Invalid or non-existent authentication information. See https://test.pypi.org/help/#invalid-auth for more information.
          9 │+  Caused by: Upload failed with status 403 Forbidden
         10 │+  Caused by: error decoding response body
         11 │+  Caused by: request or response body error
         12 │+  Caused by: error reading a body from connection
         13 │+  Caused by: stream error received: unspecific protocol error detected
────────────┴──────────────────────────────────────────────────────────────────
Stopped on the first failure. Run `cargo insta test` to run all snapshots.
test publish::invalid_token ... FAILED

failures:

failures:
    publish::invalid_token

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 1132 filtered out; finished in 64.83s


--- STDERR:              uv::it publish::invalid_token ---

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Unfiltered output ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
----- stdout -----

----- stderr -----
warning: `uv publish` is experimental and may change without warning
Publishing 1 file to https://test.pypi.org/legacy/
Uploading ok-1.0.0-py3-none-any.whl (875.0B)
error: Failed to publish `..\..\scripts\links\ok-1.0.0-py3-none-any.whl` to https://test.pypi.org/legacy/
  Caused by: Upload failed with status 403 Forbidden
  Caused by: error decoding response body
  Caused by: request or response body error
  Caused by: error reading a body from connection
  Caused by: stream error received: unspecific protocol error detected

────────────────────────────────────────────────────────────────────────────────

thread 'publish::invalid_token' panicked at E:/.cargo\registry\src\index.crates.io-6f17d22bba15001f\insta-1.40.0\src\runtime.rs:548:9:
snapshot assertion for 'invalid_token' failed in line 33

https://github.com/astral-sh/uv/actions/runs/11503449422/attempts/1?pr=8420

@zanieb zanieb added the internal A refactor or improvement that is not user-facing label Oct 24, 2024
@konstin
Copy link
Member

konstin commented Nov 3, 2024

This one is awkward because it would require retrying an error that failed with the right error code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal A refactor or improvement that is not user-facing
Projects
None yet
Development

No branches or pull requests

2 participants