retest doesn't work if not the only thing in the comment

[nikic]

If the comment issuing the /retest also contains other text (e.g. to explain why the retest is being triggered), the command may fail. It looks like

llvm-snapshots/.github/workflows/retest.yml

Line 73 in 4553e04

chroots=$(echo "${{ github.event.comment.body }}" | sed 's/^\s*\/retest\s*//g')

will treat everything except the /retest itself as the chroot list. It should only use what is on the same line instead, I think...

Example of failed workflow run: https://github.com/fedora-llvm-team/llvm-snapshots/actions/runs/10040901759

[kwk]

Yeah I saw that the other day. Thank you for tracking this here.

[kwk]

@nikic In order to change the behaviour and make it easier to use ONE /retest command inside a comment I suggest to do it this way. Say, here's a comment:

$ cat <<EOF > /tmp/foo
Suppose the command is not in the first row
      /retest     mychroot something else
And here's some explanation for why /retest foobar something completely different
it was executed.
EOF

Then this command will get mychroot and nothing else:

$ cat /tmp/foo | grep -Po '/retest\s*\K[^\s]*' --max-count=1
mychroot

Now I just need to look if this makes sense at all because of the gating that goes on before this step. But at least for now I think this should allow having an explanation after the /retest comment. (Crossing finger, this won't be picked up 🙏 )