Hi, We were wondering if *all* of the dejagnu tests should pass (in the sense that no result should be unexpected), because we have a few failed tests on our build. I will mail the summary once my current build is done.
Hi,> We were wondering if *all* of the dejagnu tests should pass (in the > sense that no result should be unexpected), because we have a few failed > tests on our build. > > I will mail the summary once my current build is done.on most platforms all tests should pass (except for those marked XFAIL, but these won't be reported as failures so no problem!). If you are building using source from svn then you may see failures from time to time, which is normal for code in development; these problems are usually fixed swiftly. Ciao, Duncan.
> We were wondering if *all* of the dejagnu tests should pass (in the > sense that no result should be unexpected), because we have a few failed > tests on our build.make check should always be clean. However, sometimes people do commit changes that impact platforms they are not able to test on and we do have the occasional failure. If you have failures, please file a bug with the test case that is failing, the command that fails, and the bc file if applicable. Basically, as much information as you can provide since it may not be a target that the majority of the developers have access to. Thanks, Tanya
Hi, Tanya M. Lattner wrote:>> We were wondering if *all* of the dejagnu tests should pass (in the >> sense that no result should be unexpected), because we have a few failed >> tests on our build. > > make check should always be clean. However, sometimes people do commit > changes that impact platforms they are not able to test on and we do have > the occasional failure. > > If you have failures, please file a bug with the test case that is > failing, the command that fails, and the bc file if applicable. Basically, > as much information as you can provide since it may not be a target that > the majority of the developers have access to.The target is OpenBSD/i386 for now and later sparc64 and amd64. Most of the errors are to do with GNU grep syntax not being compatible with BSD grep. I would not be suprised if solaris and FreeBSD were impacted by this too. The solution is to use egrep we *think*. There are a couple we are scratching our head on. One being the negative zero test. It seems the display function in llvm-dis (probably printf) is truncating the minus sign from the output deeming it pointless in the case of zero, whereas on a linux box it does not. Not sure quite what to do there yet, as -0 == 0 mathematically, but not in floating point representation. There were some others too, but off of the top of my head I cant remember. We should be able to send you guys a bunch of patches for testing soon. I think we are down to 6 failed tests now. The build itself is now reliable on OpenBSD/i386 after patching tablegen :)
On Tue, Jul 1, 2008 at 4:33 PM, Edd Barrett <vext01 at gmail.com> wrote:> Hi, > > We were wondering if *all* of the dejagnu tests should pass (in the > sense that no result should be unexpected), because we have a few failed > tests on our build. > > I will mail the summary once my current build is done.As a part of my project I had to run the Dejagnu tests several time. FYI, my Dejagnu log says: # of expected passes 2568 # of expected failures 7 -Rajika> > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >-- comp.lang.c - http://groups.google.com/group/comp.lang.c/topics -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080708/471f53fe/attachment.html>