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

problem-matcher appears to be matched in the to-test repo #21

Closed
quodlibetor opened this issue Jul 5, 2020 · 3 comments
Closed

problem-matcher appears to be matched in the to-test repo #21

quodlibetor opened this issue Jul 5, 2020 · 3 comments

Comments

@quodlibetor
Copy link
Contributor

quodlibetor commented Jul 5, 2020

My PRs just started failing with:

##[error]Unable to process command '::add-matcher::.github/problem-matcher.json' successfully.
##[error]Could not find file '/home/runner/work/chrono/chrono/.github/problem-matcher.json'.

Example: https://github.com/chronotope/chrono/pull/447/checks?check_run_id=839552633

quodlibetor added a commit to quodlibetor/rust-chrono that referenced this issue Jul 5, 2020
@quodlibetor
Copy link
Contributor Author

Seems to be related to actions/toolkit#56 which suggests that the docs say that this should have worked, but that maybe copying the file onto the host filesystem would fix it.

@ludeeus
Copy link
Owner

ludeeus commented Jul 16, 2020

Yeah, it probably needs to be in the container, or there is some magic path that should be used.
I like the problem matcher feature, so I will investigate later this week on how to safely bring it back.

@quodlibetor
Copy link
Contributor Author

yeah it seems great in general. Thanks for your work on this action!

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