Closed aap-sc closed 9 months ago
This PR should fix the issue: https://github.com/riscv-software-src/riscv-tests/issues/543
@lz-bro , @aswaterman FYI.
@en-sc could you please review this one?
Seems like the other match, which cased trouble (refs/remotes/riscv-openocd/riscv
) was added to riscv-openocd
by mistake. I have deleted it and the pipelines should work without the patch from now on (re-run example).
However, the link to riscv-openocd
repo should still be updated.
As for the part regarding revisions, I do think we can use a more robust mechanism here. I see the following alternatives:
OPENOCD_REV
to HEAD
-- this will protect against changing the default branch in riscv-openocdOPENOCD_REV
to refs/tags/latest
-- this is the tag, updated by snapshot.yml
workflow on push. IMHO, this is the best option, since this tag is the closest thing to a release in riscv-openocd
.I have deleted it and the pipelines should work without the patch from now on ([re-run example]
Yep. It works now. I'll abandon the patch then
git ls-remote
lists bothrefs/head
andrefs/remotes
. riscv-openocd got a new entry in refs/remotes that matchesriscv
pattern around Jan 25. This breaks gitlab pipeline. The commit restricts ls-remote only torefs/head
.In addition this commit changes the address of riscv-openocd repository, since it was moved to riscv-collab space a while ago.