>You should really subscribe to commits@flex.apache.org, the relevant parts of the logs
are inline in the emails.
I have subscribed a while ago to commits.
The email notification starts with:
[...truncated 86284 lines...]
[java] After Wait loop 12:50:01.447 waiting = 0
[java] clobberProcess false
[java] Total Results so far: 1
(and the root cause of the failure is in the truncated 86284).
>I don't have time or knowledge to make the Mustella VM accessible for the outside world
in a secure and easily maintainable fashion.
>It is however accessible to PMC members, the credentials are in the archives of the >private@flex.apache.org.
Ok, I will check the private archive.
Another possibility would be to configure the jenkins mustella job so that failure notifications
emails include a zip of the full build log (untruncated).
Maurice
-----Message d'origine-----
De : Erik de Bruin [mailto:erik@ixsoftware.nl]
Envoyé : lundi 2 décembre 2013 19:34
À : dev@flex.apache.org
Cc : commits@flex.apache.org; jmclean@apache.org
Objet : Re: Build failed in Jenkins: flex-sdk_mustella #577
You should really subscribe to commits@flex.apache.org, the relevant parts of the logs are
inline in the emails.
I don't have time or knowledge to make the Mustella VM accessible for the outside world in
a secure and easily maintainable fashion. It is however accessible to PMC members, the credentials
are in the archives of the private@flex.apache.org.
EdB
|