On Wed, Feb 20, 2019 at 03:04:51PM +0100, Tomasz Kłoczko wrote: > OK. Jakub so what kind of method you are using to recognise that something > is wrong with gcc/gdb/binutils if none of those packages test suites seems > may exit with non-zero exit code and some failures are perfectly OK? > (Or maybe logic of the suite should be negated?) > Do you have some sort of script/tool extracting results from build logs? or > it is some other method? > Syntax of the content /^==*TESTING/,/^==*TESTING END/p' looks a bit > complicated .. > How to trace those results in more or less automated way? It is intentionally a manual process. For koji, my current script is: #!/bin/sh vr=`echo $2 | sed 's,/,-,'` mkdir -p ~/tool-test/$1/$vr for arch in i686 x86_64 armv7hl ppc64 ppc64le aarch64 s390 s390x ppc; do ar=`echo $arch | sed 's/armv7hl/armhfp/;s/i686/i386/'` wget http://kojipkgs.fedoraproject.org/packages/$1/$2/data/logs/$arch/build.log -O ~/tool-test/$1/$vr/$ar if [ ! -s ~/tool-test/$1/$vr/$ar ]; then rm ~/tool-test/$1/$vr/$ar; continue; fi sed -n -i -e '/^==*TESTING/,/^==*TESTING END/p' ~/tool-test/$1/$vr/$ar done which populates the directories, and then I just diff -uprN ~/tool-test/gcc/9.0.1-0.{3,4}.fc30 and use my own judgement of what is and what isn't a blocker and what needs to be fixed even if it is not a blocker. Jakub _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
