From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,e36d34be7cedff0e X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news1.google.com!newsfeed.gamma.ru!Gamma.RU!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.cw.net!cw.net!news-FFM2.ecrc.de!news0.de.colt.net!news-fra1.dfn.de!newsfeed.pionier.net.pl!pwr.wroc.pl!panorama.wcss.wroc.pl!not-for-mail From: Waldek Hebisch Newsgroups: comp.lang.ada Subject: Re: ACATS Random failure under GNAT GCC Date: Thu, 23 Feb 2006 01:09:16 +0000 (UTC) Organization: Politechnika Wroclawska Message-ID: References: <1139766766.085134.134180@f14g2000cwb.googlegroups.com> NNTP-Posting-Host: hera.math.uni.wroc.pl X-Trace: panorama.wcss.wroc.pl 1140656956 25776 156.17.86.1 (23 Feb 2006 01:09:16 GMT) X-Complaints-To: abuse@news.pwr.wroc.pl NNTP-Posting-Date: Thu, 23 Feb 2006 01:09:16 +0000 (UTC) User-Agent: tin/1.7.8-20050315 ("Scalpay") (UNIX) (Linux/2.4.31 (i686)) Xref: g2news1.google.com comp.lang.ada:3084 Date: 2006-02-23T01:09:16+00:00 List-Id: Anh Vo wrote: > I have noticed that ACATS randomly fails in gcc 4.0.x and 4.1.x. under > RH 8.0 and 9.0. Normally, it does happen when it is built and tested > the firtst time. After that if ACATS is tested again consecutively, for > example with three consecutive commands make -C gcc check-ada; make -C > gcc check; make -C gcc check-ada, a small number of ACATS failures show > up. So far, for gcc-4.0.x the tests below have failed. > > FAIL: c94001c > FAIL: c954025 > FAIL: cd7101f > FAIL: cd7103d > FAIL: cd7204b > FAIL: ce3804b > > For gcc-4.1.x there are two ACATS tests have failed. > > FAIL: ce2401l > FAIL: ce3906f > > Has anyone expericenced with this situation or just me? I would like > hear your suggestion before reporting to gcc. > I have no experience with ACATS. But I got random errors in C testsuite. AFAIK the reason was bug in test environment (expect): it was unable to correctly capture program output. -- Waldek Hebisch hebisch@math.uni.wroc.pl