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

Error: no files matched to [**/requirements.txt or **/pyproject.toml] #76

Closed
nicoddemus opened this issue Nov 1, 2023 · 8 comments
Closed

Comments

@nicoddemus
Copy link

Hi,

Recently I started seeing errors in a few repositories like this when using the action:

Error: No file in /home/runner/work/pytest-cpp/pytest-cpp matched to [**/requirements.txt or **/pyproject.toml], make sure you have checked out the target repository

AFAICT nothing has changed in the repositories significantly, in fact the errors appeared during pre-commit updates.

Is a requirement for projects to always have a pyproject.toml in the root now? Or something else?

Links to the failures (all of them are using the latest version, 1.5.3):

https://github.com/pytest-dev/pytest-cpp/actions/runs/6720286585/job/18263515881?pr=125
https://github.com/gabrielcnr/pytest-datadir/actions/runs/6697263629/job/18196747120?pr=72

@hynek
Copy link
Owner

hynek commented Nov 1, 2023

ah crap I think that's the attempt to use pip caching. i'll push 1.5.4 in a minute.

@hynek
Copy link
Owner

hynek commented Nov 1, 2023

Would you mind testing in one of those projects with a pin to d3afbdcb2e3582389a03994cd76eb496b951f20c if it helps? It should, but I'd prefer to not botch another release.

@nicoddemus
Copy link
Author

Sure, 1min

@nicoddemus
Copy link
Author

@hynek
Copy link
Owner

hynek commented Nov 1, 2023

w00t, thanks! I'll release right away.

@hynek hynek closed this as completed Nov 1, 2023
@nicoddemus
Copy link
Author

Great, thanks a lot for the lightning fast response!

@hynek
Copy link
Owner

hynek commented Nov 1, 2023

1.5.4 (works as 1.5 and 1) is out – lmk if something still goes wrong :)

@nicoddemus
Copy link
Author

I can confirm using just v1.5 works. Thanks again!

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

No branches or pull requests

2 participants