Hi Indu! I recently saw that you just started contributing to GCC, so: welcome, and enjoy to journey!
On Mon, 10 Dec 2018 12:54:09 -0800, Indu Bhagat <indu.bha...@oracle.com> wrote: > On 12/06/2018 05:54 PM, Indu Bhagat wrote: > > [...] Thanks for looking into this issue again. As I said in private email, such things (like looking at the wrong build's test logs) happen to all of us. As long as we learn -- or, at least try to learn ;-) -- something from that, that's fine, as far as I'm concerned. Evidently, the peer review/collaboration that we have in these Free Software/Open Source software projects worked, and we eventually caught this issue. :-) > > 2. I do however see other tests (a total of 23) which are have > > regressed from > > PASS --> UNRESOLVED. A diff is attached. > > > > Each one of them is due to "Error/Warning threshold exceeded: 1 0 > > (max. 1 3)" > False alarm. > > Looks like there is some flakiness I ran into. Anything we could help you with, or that you have questions about? > New testsuite runs (make check-gcc) on a fresh builds of the GCC (with > and without missing-profile) enabled look OK. > One additional failure as expected (Wmissing-profile.c). No additional > unresolved tests. Good, thanks for verifying! Grüße Thomas
