Skip to content

Too many pfam tests so GitHub Actions checks often fail #2182

@jamesmkrieger

Description

@jamesmkrieger

Note: Our GitHub Issues are for bug reports ONLY. Please post any feature requests and other topics to the Discussions tab. Thank you.

Please read the following before posting an issue.
Hello, we are sorry that you have run into a problem while using ProDy. We will do our best to address your issues in a timely and comprehensive manner. In return, we ask that you completely fill out this bug report. Do not leave any section blank. Filling this form out ensures that we can help you most efficiently and saves us (and you) time and energy. Also, please search old issues and discussions before opening a new Issue. Chances are, someone in the past had your issue and the solution was described there.

Description of the bug.

Github Actions checks often fail because we are sending too many requests to pfam. This is a combination of running 6 sets of checks at the same time and having many tests for pfam inside each set.

Do you have any error messages or logs?

Error logs can be seen in actions for pull requests, including https://github.com/prody/ProDy/actions/runs/18718269028/attempts/1 as one of the most recent. They can sometimes come out differently e.g. #1933 and links there such as https://github.com/prody/ProDy/actions/runs/17093535125/job/48472530986

What is your setup?

This happens for both Linux and MacOS checks regardless of Python version.

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions