Recently I've been trying to trace some gcc issue so I've downloaded my gcc
src.rpm to try to build my own package.
During review build log I found a lot of test suite failures.
Initially I've been thinking that something is wrong with my devel env so
I've peaked on official gcc build logs and I found that I have even less
such failures than number of such issues on rawhide builders.

Mine package:

$ grep ^FAIL: -c gcc.out
780

Vs. official:
$ curl -s
https://kojipkgs.fedoraproject.org//work/tasks/681/32910681/build.log |
grep -c FAIL:
1114

Some of those failures seems are expected as I'm able to find in my build
log fragments like:

                === gnat Summary for unix/ ===

# of expected passes            2976
# of expected failures          23
# of unsupported tests          3

However I found other like:

                === gcc Summary for unix/ ===

# of expected passes            143765
# of unexpected failures        101
# of unexpected successes       25
# of expected failures          554
# of unsupported tests          2225

Did all those unexpected failures are symptoms some not finished
modifications and/or not updated test units or those failures says that
something really is wrong with gcc?

At the moment I'm not sure but I think that similar situation is with
binutils but I think that generally during my build I saw a lot of
failures. All together all those tests have been ignored and package build
was successful.

kloczek
-- 
Tomasz Kłoczko | LinkedIn: *http://lnkd.in/FXPWxH <http://lnkd.in/FXPWxH>*
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Reply via email to