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

Pull request hook fails to find pathspec #126

Open
rotu opened this issue Apr 1, 2020 · 4 comments
Open

Pull request hook fails to find pathspec #126

rotu opened this issue Apr 1, 2020 · 4 comments
Labels
bug Something isn't working

Comments

@rotu
Copy link
Contributor

rotu commented Apr 1, 2020

Description

CI fails to find pathspec for pull request hook. I believe it’s likely looking at the wrong remote for the vcs import step (the targeted repo versus the repo containing the pull request hook)

Expected Behavior

PR branch is pulled in and tested.

Actual Behavior

Failure log:

https://github.com/ros2/rmw_cyclonedds/runs/551468986?check_suite_focus=true

bash -c vcs import src/ < package.repo
1290
  === src/rmw_cyclonedds (git) ===
1291
  Could not checkout ref 'readme-edits': error: pathspec 'readme-edits' did not match any file(s) known to git
@rotu rotu added the bug Something isn't working label Apr 1, 2020
@emersonknapp
Copy link
Contributor

This seems to happen occasionally, maybe we need some retry logic around the checkout.

@emersonknapp emersonknapp added bug Something isn't working and removed bug Something isn't working labels Nov 6, 2020
@christophebedard
Copy link
Member

@rotu @emersonknapp is this still happening? The CI job logs are gone so I'm not sure how to go about reproducing this.

@emersonknapp
Copy link
Contributor

I have seen this happen occasionally, yes, but I don't have any concrete examples to point to right now. I have also seen it happen on the ci.ros2.org buildfarm, so I'm fairly certain it's not specifically an action-ros-ci issue - but if we can do anything to mitigate it, that would be valuable

@christophebedard
Copy link
Member

I see. Then if it's just a git/network flakiness issue, --retry N (with vcs import) can probably help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants