[igt-dev] [PATCH i-g-t 2/2] gitlab-ci: Verify blacklist files with verify-blacklist.sh

[Petri Latvala]

On Fri, Jun 12, 2020 at 03:52:47PM +0300, Arkadiusz Hiler wrote:
> On Fri, Jun 12, 2020 at 11:57:14AM +0300, Petri Latvala wrote:
> > On Fri, Jun 12, 2020 at 11:51:35AM +0300, Petri Latvala wrote:
> > > Signed-off-by: Petri Latvala <petri.latvala at intel.com>
> > > Cc: Arkadiusz Hiler <arkadiusz.hiler at intel.com>
> > 
> > FYI: https://gitlab.freedesktop.org/adrinael/igt-gpu-tools/-/jobs/3073434
> > 
> > Verifying took 5 minutes on gitlab, but that's parallelized with the
> > other test-stage executions.
> 
> But it's also the slowest step of that stage by far. Even the qemu
> cross-testing is ~5x faster.
> 
> Doing:
> > if ! "$RUNNER" --list-all --include-tests "$test" "$BINDIR" >/dev/null 2>/dev/null; then
> for each blacklist entry is a bit expensive. It execs all the test
> binaries each time.
> 
> Something like this should be faster:
> 
> TESTLIST="$("$RUNNER" --list-all "$BINDIR")"
> 
> cat "$BLFILE" | while read line; do
>     blentry=$(echo "$line" | sed 's/#.*//' | tr -d '[:space:]')
>     if [ "$blentry" = "" ]; then continue; fi
> 
>     if ! (echo "$TESTLIST" | grep -q "$blentry") >/dev/null 2>/dev/null; then
>         echo Useless blacklist entry: "$blentry"
>        STATUS=1
>     fi
> done
> 
> This may be not exactly the same as runner is using glib's regex, but if
> you switch it to PCRE then 'grep -P' should be close enough.


Meh, fair enough. I was doing it this way to make sure we process the
blacklist exactly the same way in the check as in "production", and I
can't remember now what my real fear was. Extending the blacklist
syntax? We're going to catch that on first use on some level of
confidence and even if we don't it's not a big deal.

New revision with new numbers on its way!


-- 
Petri Latvala