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

Hit test-pypi memory limit #60

Closed
SimeonStoykovQC opened this issue Jan 19, 2023 · 1 comment · Fixed by #61
Closed

Hit test-pypi memory limit #60

SimeonStoykovQC opened this issue Jan 19, 2023 · 1 comment · Fixed by #61

Comments

@SimeonStoykovQC
Copy link
Member

SimeonStoykovQC commented Jan 19, 2023

There is a workflow that tries to upload the package to TestPyPI, and it started failing with:

WARNING  Error during upload. Retry with the --verbose option for more details. 
ERROR    HTTPError: 400 Bad Request from https://test.pypi.org/legacy/          
         Project size too large. Limit for project 'pytsql' total size is 10 GB.
         See https://test.pypi.org/help/#project-size-limit  

image

This should not be critical.

We could consider:

  1. Deleting what's already there to free up all space and deal with this when it happens again
  2. Disable the workflow that uploads to testpypi
@ivergara
Copy link
Collaborator

I don't think it makes sense to upload to TestPyPI for every branch. Also, since I don't think anyone is actually making sure that whatever is pushed to TestPyPI is actually installable and working, it has no compelling purpose.

Maybe it'd make sense for tags that are meant to be released but then pushing to PyPI upon tag wouldn't make much sense.

My take, is just to remove the publish to TestPyPI altogether.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants