https://bugs.documentfoundation.org/show_bug.cgi?id=162126

Buovjaga <ilmari.lauhakan...@libreoffice.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
                 CC|                            |ilmari.lauhakangas@libreoff
                   |                            |ice.org
           Keywords|                            |bibisectRequest, regression
             Status|UNCONFIRMED                 |NEW

--- Comment #2 from Buovjaga <ilmari.lauhakan...@libreoffice.org> ---
This seems difficult to bisect.

I adapted a script from
https://wiki.documentfoundation.org/QA/Bibisect/Automation like this:

#!/usr/bin/env bash
# bisect_perf.sh  Called with 3+1 parameters: "file.ext" good-time timeout-time
[fix]
    fileext=$1 ;   goodtime=$2 ; timeouttime=$3 ; regfix=$4
    if [[ $regfix = "fix" ]]; then before=1; after=0; else before=0; after=1;
fi
    # timeout takes seconds by default
    timeout $timeouttime bash -c ' OOO_EXIT_POST_STARTUP=1
SAL_USE_VCLPLUGIN=gen ./instdir/program/soffice --norestore "$@" ' bash 
/home/user/libobugs/"$fileext"
    status=$? ;         echo "$status"
    exptime=$SECONDS
        if [ $status = 124 ] ; then
                echo "timeout in $timeouttime, done in $exptime sec" ; exit
$before
        elif [ $status = 134 ] ; then
            echo "done in $exptime sec" ; exit $after
        elif [ $status = 42 ] ; then
            if (( $exptime < $goodtime ))  ; then
                echo "opens fast in $exptime sec" ; exit $before
            elif (( $exptime > $goodtime ))  ; then
                echo "opens slow in $exptime sec" ; exit $after
            else echo "error"
            fi
        else echo "other exit code"
    git reset --hard
    fi

Then started a run with it in the Linux 24.2 repo, which seemed to be the one
where it slowed down:

git bisect start master oldest && git bisect run /path/to/bisect_perf.sh
"Тест.xlsx" 80 240

Limit for good being 80 secs and timeout being 4 minutes. However, the results
were not reliable in the actual bisecting run. The original bad time I saw was
like 2min30sec, but in the bisect run I got many timeouts, so going over 4
mins. Doing the run a couple of times and checking the blamed vs. previous
commit revealed the result was incorrect.

I may continue investigating this.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to