@cj5716 i think the tests failed because you are missing a : in the bench

@cj5716 i think the tests failed because you are missing a : in the bench

That's optional, The test is falling on all the other 4 PRs, the check-includes are failing.

@peregrineshahin no, on this the Stockfisch tests are failing as well.

the : is optional here

          for hash in $(git rev-list -100 HEAD); do
            benchref=$(git show -s $hash | tac | grep -m 1 -o -x '[[:space:]]*\b[Bb]ench[ :]\+[1-9][0-9]\{5,7\}\b[[:space:]]*' | sed 's/[^0-9]//g') && break || true
          done

I see but still the CI extracted a wrong bench related to this pr https://github.com/official-stockfish/Stockfish/actions/runs/7054420272/job/19203254803. This should be unrelated to the analyzer failing issue

It's failing because it's not written on a separate line in the commit message.
Do you think such a thing should be a requirement?
I don't think is is how it's done in fishtest even in my PR https://github.com/official-stockfish/fishtest/pull/1840/files

my_string="somemessage   Bench: 98765432"
result=$(echo "$my_string" | tac | grep -m 1 -o -x '[[:space:]]*\b[Bb]ench[ :]\+[1-9][0-9]\{5,7\}\b[[:space:]]*' | sed 's/[^0-9]//g')
echo "Extracted benchmark value: $result"

this does not match....

Ah I see thanks. I think a separate line is fine but should probably be documented somewhere if that’s not the case already.

Ah I see thanks. I think a separate line is fine but should probably be documented somewhere if that’s not the case already.

Well we accept non-separate lines in fishtest, many devs use this when testing because they don't worry about adding a description.
Sometimes like "Take 1 bench: 9999999" in one line.

However, in PR'ing here it looks inconsistent that Stockfish CI does not accept it..