Skip to content

Error fetching remote repo on node-test-commit-v8-linux #4507

Open

Description

@aduh95

https://ci.nodejs.org/job/node-test-commit-v8-linux/7423/console

 > git fetch --no-tags --force --progress --depth=100 -- git@github.com:nodejs/node.git +refs/heads/*:refs/remotes/origin/* +refs/pull/66089/head:refs/remotes/origin/_jenkins_local_branch # timeout=20
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from git@github.com:nodejs/node.git
	at PluginClassLoader for git//hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:998)
	at PluginClassLoader for git//hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1239)
	at PluginClassLoader for git//hudson.plugins.git.GitSCM._checkout(GitSCM.java:1310)
	at PluginClassLoader for git//hudson.plugins.git.GitSCM.checkout(GitSCM.java:1277)
	at hudson.scm.SCM.checkout(SCM.java:540)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1254)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:648)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:84)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521)
	at hudson.model.Run.execute(Run.java:1849)
	at PluginClassLoader for matrix-project//hudson.matrix.MatrixBuild.run(MatrixBuild.java:331)
	at hudson.model.ResourceController.execute(ResourceController.java:97)
	at hudson.model.Executor.run(Executor.java:456)
Caused by: hudson.plugins.git.GitException: Command "git fetch --no-tags --force --progress --depth=100 -- git@github.com:nodejs/node.git +refs/heads/*:refs/remotes/origin/* +refs/pull/66089/head:refs/remotes/origin/_jenkins_local_branch" returned status code 1:
stdout: 
stderr: remote: Enumerating objects: 327, done.        
…
From github.com:nodejs/node
   6d5e3098711..f9defa61fa9  main                    -> origin/main
error: cannot lock ref 'refs/remotes/origin/revert/doc-kit-redesign': 'refs/remotes/origin/revert' exists; cannot create 'refs/remotes/origin/revert/doc-kit-redesign'
 ! [new branch]              revert/doc-kit-redesign -> origin/revert/doc-kit-redesign  (unable to update local ref)
 + 6d5e3098711...7511323e386 refs/pull/66089/head    -> origin/_jenkins_local_branch  (forced update)
error: some local refs could not be updated; try running
 'git remote prune git@github.com:nodejs/node.git' to remove any old, conflicting branches

	at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2852)
	at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2193)
	at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:638)
	at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:173)
	at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:164)
	at hudson.remoting.UserRequest.perform(UserRequest.java:225)
	at hudson.remoting.UserRequest.perform(UserRequest.java:50)
	at hudson.remoting.Request$2.run(Request.java:391)
	at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:81)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:328)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1090)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
	at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:312)
	at java.base/java.lang.Thread.run(Thread.java:1474)
	Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 8.225.232.44/8.225.232.44:43584
		at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1916)
		at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:384)
		at hudson.remoting.Channel.call(Channel.java:1108)
		at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:155)
		at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
		at java.base/java.lang.reflect.Method.invoke(Method.java:580)
		at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:140)
		at PluginClassLoader for git-client/jdk.proxy72/jdk.proxy72.$Proxy156.execute(Unknown Source)
		at PluginClassLoader for git//hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:996)
		at PluginClassLoader for git//hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1239)
		at PluginClassLoader for git//hudson.plugins.git.GitSCM._checkout(GitSCM.java:1310)
		at PluginClassLoader for git//hudson.plugins.git.GitSCM.checkout(GitSCM.java:1277)
		at hudson.scm.SCM.checkout(SCM.java:540)
		at hudson.model.AbstractProject.checkout(AbstractProject.java:1254)
		at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:648)
		at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:84)
		at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521)
		at hudson.model.Run.execute(Run.java:1849)
		at PluginClassLoader for matrix-project//hudson.matrix.MatrixBuild.run(MatrixBuild.java:331)
		at hudson.model.ResourceController.execute(ResourceController.java:97)
		at hudson.model.Executor.run(Executor.java:456)
ERROR: Error fetching remote repo 'origin'
Collecting metadata...
Metadata collection done.
[Checks API] No suitable checks publisher found.
Notifying upstream projects of job completion
Notifying upstream of completion: node-test-commit-v8-linux #7414
[Join] Pending does not contain node-test-commit-v8-linux
Finished: FAILURE

Activity

  1. richardlau commented on Oct 8, 2026

    @richardlau
    Member

    It's not just node-test-commit-v8-linux. Several jobs are affected, including the more commonly run ones under node-test-commit.

    The relevant part of the log is

    error: cannot lock ref 'refs/remotes/origin/revert/doc-kit-redesign': 'refs/remotes/origin/revert' exists; cannot create 'refs/remotes/origin/revert/doc-kit-redesign'
    

    and I don't know yet if that is a local workspace issue on something that's going to reoccur due to the upstream references from the nodejs/node repository.

  2. richardlau commented on Oct 8, 2026

    @richardlau
    Member

    refs/remotes/origin/revert/doc-kit-redesign is from nodejs/node#66572, which is closed. I'll delete the branch from https://github.com/nodejs/node.

  3. richardlau commented on Oct 8, 2026

    @richardlau
    Member

    I'm not sure where refs/remotes/origin/revert is from. It's not a current branch on https://github.com/nodejs/node and is probably historical (but no idea how far back). Unfortunately since the git credentials are passed through Jenkins I can't easily check directly on the machine. Worst case is we'd need to wipe out the workspaces on all affected machines. I'll start a few test jobs now that the other branch has been deleted and see if that's enough to fix the issue or if we'll need to wipe out each workspace (including the @number suffixed ones).

    In practice, this should only be an issue with branches created directly on https://github.com/nodejs/node, which isn't supposed to be common as we encourage contributions from forks.

  4. richardlau commented on Oct 8, 2026

    @richardlau
    Member

    https://ci.nodejs.org/job/node-test-commit-v8-linux/7424/ got past the git issue, but has hit a different problem (I'll open another issue to track).

  5. aduh95 commented on Oct 8, 2026

    @aduh95
    ContributorAuthor

    refs/remotes/origin/revert/doc-kit-redesign is from nodejs/node#66572, which is closed. I'll delete the branch from https://github.com/nodejs/node.

    I wonder how this happened, https://github.com/nodejs/node/settings/rules/714753 is supposed to block creation of branches on nodejs/node. @avivkeller did you do something special to create that branch?

  6. avivkeller commented on Oct 8, 2026

    @avivkeller
    Member

    Nope! I was a bit rushed to make the revert, and accidentally pushed to origin into instead of avivkeller

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions