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

fetch error: lock file exists #758

Open
geigerzaehler opened this issue Aug 17, 2021 · 0 comments
Open

fetch error: lock file exists #758

geigerzaehler opened this issue Aug 17, 2021 · 0 comments

Comments

@geigerzaehler
Copy link
Contributor

We sometimes see the following errors on CI

fetch error
  urn=rad:git:hnrkycwsgjfsczs3reyjoomhra38h85jo87ky
  remote_peer=hyyf6aqsao5yjcnx49ohi4mkwenrf7dwm5gmmw9kn1a63dagxrqrn6
  error=Replication(Fetch(Git(Error { code: -1, klass: 2, message: "failed to create locked file '/usr/local/var/buildkite-agent/builds/mac-n-cheese-local/monadic/radicle-upstream/cypress/workspace/test-tmp/patches -- updates maintainer view when a patch has been received.9ab5/node-17000/0914c5d2-b619-4268-b0e1-672ab513a704/git/refs/namespaces/hnrkycwsgjfsczs3reyjoomhra38h85jo87ky/refs/remotes/hyyf6aqsao5yjcnx49ohi4mkwenrf7dwm5gmmw9kn1a63dagxrqrn6/tags/radicle-patch/feature-1.lock': File exists" })))

To me it looks like the calls to librad::git::replication::replicate() issued by librad::net::peer::Storage::put as a response to gossip messages and by regular calls to daemon::peer::sync::sync() race.

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

1 participant