On Feb 6, 2007, at 6:29 PM, Gregory Shimansky wrote:
Geir Magnusson Jr. wrote:
On Feb 6, 2007, at 5:48 PM, Gregory Shimansky wrote:
Geir, such messages are counter productive.
It's not counter productive, just incomplete :)
Could you at least write on what platform you're running the
tests? I've just ran the tests on my bleeding edge Gentoo
installation on x86 and they all passed. So no, I don't see drlvm
tests failing.
I'm just watching my machines (ubuntu x86) and getting failures.
I'm testing again to narrow it down. I was also watching the
alerts stream and we had by my count 10 failure messages today...
Speaking of which I was going to ask this question a long time ago.
I am not understanding these alerts at all.
I am seeing a message like this (skipping unnecessary whitespace):
[build-test alert] BUILD FAILED lnx gcc debug: drlvm
Errors/Warnings: (1)
Unit Tests: (2310)
All Tests Passed
and wonder why the preceeding message like this
[build-test alert] BUILD SUCCEEDED lnx gcc debug: classlib over drlvm
Errors/Warnings: (169)
Unit Tests: (19455)
All Tests Passed
was actually successful when there were 169 errors/warnings and in
the first it was only 1.
These alerts contain so little information that it is impossible to
understand if it is a bug in the scripts (which I tend to think so
far) or something really is broken.
This is exactly one of my things to do this week - I can make *zero*
sense of these things. I will put in the XML snippet that we talked
about so we have identifying information (which machine, OS, version
of gcc, etc), and then try to get the breakage info into the script,
rather than the junk that's there now.
I'll also go through the JIRAs - it seems like we aren't all running
the same thing. I've never sent out a "fixed" message, for example.
geir
--
Gregory
