And another new AB-INT, probably just some short issue on the infrastructure. INFO: No remote repository configured, use provided url Traceback (most recent call last): File "/srv/pokybuild/yocto-worker/buildperf-debian11/build/layers/openembedded-core/meta/lib/oeqa/utils/gitarchive.py", line 118, in get_tags tags_refs = repo.run_cmd(cmd) ^^^^^^^^^^^^^^^^^ File "/srv/pokybuild/yocto-worker/buildperf-debian11/build/layers/openembedded-core/meta/lib/oeqa/utils/git.py", line 62, in run_cmd return self._run_git_cmd_at(git_args, self.top_dir, env=env) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/srv/pokybuild/yocto-worker/buildperf-debian11/build/layers/openembedded-core/meta/lib/oeqa/utils/git.py", line 43, in _run_git_cmd_at raise GitError("'{}' failed with exit code {}: {}".format( oeqa.utils.git.GitError: 'git ls-remote --refs --tags -q origin' failed with exit code 128: fatal: 'origin' does not appear to be a git repository fatal: Could not read from remote repository. I believe the said remote is "git@push.yoctoproject.org:yocto-buildstats", which is working fine now. Still opening a ticket to track the occurrences.
buildperf-debian11 perf-debian12-vk master completed at 2025-12-31 11:20:48+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/84/builds/2005/steps/12/logs/stdio
Need proof to confirm the suspicion that it's an intermittent network problem.
Not occurring frequently, and there have been significant infrastructure improvements, let's close this.