For the record, this time it wasn't Xvfb at fault.

It was that we'd mistakenly used "x86" in our architecture setting instead of "ppc".
Aparently, someone took someone else's word that you could just "check out the starting build scripts from cvs"  :)
From now on, I'll strive to leave the head version of releng.control in an eclipse-build-mahine-ready state.
Ohter, local build machines may then have to change some parameters, but that's the way it should be.

Thanks all.




Naci Dai <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]

10/31/2006 09:24 AM

Please respond to
"General discussion of project-wide or architectural issues."        <[email protected]>

To
"General discussion of project-wide or architectural issues." <[email protected]>
cc
[EMAIL PROTECTED]
Subject
Re: [wtp-dev] Attention needed for M3 based builds





David,

I think you are dead on right, Xvfb is not running on the build server anymore.  I think we will have to ask our friendly webmaster to brignt it back to life.




Also,
The massive failures in JUnit plugins are being investigated by the experts (i.e. Naci)
It seems to be only the "UI tests" that are failing ... so, I suspect, something's changed with our Xvfb server

on our build machine.






_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
 



--
Naci Dai,

eteration a.s.
itu teknokent ari-1 25
Maslak, Istanbul 34469

+90 (533) 580 2393 (cell)
+90 (212) 328 0825 (phone)
+90 (212) 328 0521 (fax)
http://www.eteration.com/
mailto:[EMAIL PROTECTED]_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev

_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Reply via email to