I'd love for (something like) gcc-testresults@ to be usefully
searchable (it can be done but... lacks), so please allow me:
On Fri, 13 Sep 2024, Frank Ch. Eigler wrote:
> diff --git a/contrib/test_summary b/contrib/test_summary
> index 5760b053ec27..867ada4d6b81 100755
> --- a/contrib/test_summary
> +++ b/contrib/test_summary
> @@ -39,6 +39,9 @@ if test x"$1" = "x-h"; then
> should be selected from the log files.
> -f: force reports to be mailed; if omitted, only reports that differ
> from the sent.* version are sent.
> + -b: instead of emailing, push test logs into a bunsen git repo
> + -bg REPO: specify the bunsen git repo to override default
> + -bt TAG: specify the bunsen git commit tag to override default
> _EOF
> exit 0
> fi
> @@ -57,6 +60,9 @@ fi
> : ${filesuffix=}; export filesuffix
> : ${move=true}; export move
> : ${forcemail=false}; export forcemail
> +: ${bunsen=false};
> +: ${bunsengit=ssh://sourceware.org/git/bunsendb.git/};
> +: ${bunsentag=`whoami`/gcc/`uname -m`-`date +%Y%m%d-%H%M`};
That uname -m looks like it's an assumption that the report is
for a 1) native build that is 2) the same machine as where the
git push should happen and 3) all run the same OS. Also, my
local account-name may be completely different than what's
needed in the tag. Looks like there's a side-question for
account names for the bunsendb when you don't have a sourceware
account (are rules needed)? Anyway, please parametrize.
Please instead of uname -m scrape the default target identifier
from the build.
Use-case: I push cross-build reports from an entirely different
machine. My local login may be different.
brgds, H-P
