DEV300_m68/DEV300_m69 solaris buildbots die in soltools
http://buildbot.go-oo.org/buildbot/builders/Solaris-Sparc/builds/1567/steps/Compile/logs/stdio
i.e.
Error: Could not open include filemap.
Error: Could not open include filestring.
Error: Could not open include fileiostream
etc., seeing
Kurt, all,
Was it not decided to commit masterfixes directly to
hg.services.openoffice.org/DEV300, instead of including them in
hg.services.openoffice.org/re/DEV300_next (as has apparently happened
with the below
http://hg.services.openoffice.org/re/DEV300_next/rev/539b01f994d3)?
-Stephan
Hi! I'm the Asturian language coordinator.
Can you add my language into the QATrack web, please? (I can't choose
my language).
http://qatrack.services.openoffice.org/languages.php
Thanks very much!
Best regards.
-
To unsubscribe,
Hi Stephan,
no, the decision was to put only final milestone builds to
hg.services.openoffice.org/DEV300. All other stuff like masterfixes and
integrations for the next milestone should go to
hg.services.openoffice.org/re/DEV300_next.
Kurt
Stephan Bergmann schrieb:
Kurt, all,
Was it not
On 01/15/10 12:19, Kurt Zenker wrote:
no, the decision was to put only final milestone builds to
hg.services.openoffice.org/DEV300. All other stuff like masterfixes and
integrations for the next milestone should go to
hg.services.openoffice.org/re/DEV300_next.
I think I remember there was some
Hi
Iam Software Engineer by proffession and I would like to contribute the
development activities of OpenOffice
Please let me know how can I begin, I leave in Sing.apore
Thanking you
With best regards
Raghu
Hi
fixed the soli buildbot yesterday and the sparc one today. everything
should be fine now
BTW: investigating with kurt why the smoketest on an m8 times out
Cheers
Gregor
Caola'n McNamara schrieb:
DEV300_m68/DEV300_m69 solaris buildbots die in soltools