-
Notifications
You must be signed in to change notification settings - Fork 208
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
Skip symlinks in enqueue_git_update_all #5951
Conversation
2ace7d9
to
22e4527
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5951 +/- ##
=======================================
Coverage 98.75% 98.75%
=======================================
Files 396 396
Lines 38966 38966
=======================================
Hits 38479 38479
Misses 487 487 ☔ View full report in Codecov by Sentry. |
24c1ad4
to
e7da05c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess you need to extend tests according to the codecov report
No, codecov just didn't run on my force push yet |
8b49b5a
to
d299c40
Compare
I reduced this PR to only the first commit about using |
@Mergifyio rebase |
I forgot that `-d` is actually true for symlinks. It resulted in the gru task processing over the same realpaths, trying to get a guard for the same path multiple times, which failed and ran int an endless retry. Issue: https://progress.opensuse.org/issues/164898
✅ Branch has been successfully rebased |
I forgot that
-d
is actually true for symlinks.It resulted in the gru task processing over the same realpaths, trying
to get a guard for the same path multiple times, which failed and ran
int an endless retry.
Issue: https://progress.opensuse.org/issues/164898
I tested it locally with symlinks and could now reproduce the problem. It tries to get a guard for the same directory multiple times and runs into an endless retry.