M5 spin status :: no aggregate or JBDS installers available yet; many bot and non-UI test failures, plus one inter-build compilation failure
by Nick Boldt
Since turning on the stable branch jobs, here's what's borked...
https://issues.jboss.org/browse/JBIDE-10349
Still trying to get a clean stable_branch aggregate build (and then JBT
builds too) - last time the aggregate failed due to missing Central,
OTDT, and OpenShift (hadn't spun clean yet).
---
Details:
- hibernate : test failure in org.hibernate.eclipse.console.test
- jbpm : test failure in org.jboss.tools.jbpm.convert.test
- jsf : test failure in org.jboss.tools.jsf.vpe.jsf.test
- maven : 15 bot test failures (same failures in trunk) ... should these
just be turned off and only run locally / manually?
- struts : COMPILE FAILED - upstream bits missing? "The import
org.jboss.tools.jst.web.validation cannot be resolved."
---
There are also a few jobs for which the latest build failed, but at
least we have one good build since branching. This suggests we're having
some stability issues w/ a few Jenkins slaves, but at least we're
getting clean spins when the server is quiet(er).
= archives : aborted build? [Dec 4 ok]
= birt : failed to find usage bits (poor timing between builds) [Dec 4 ok]
= seam : no more locks failure [Dec 4 ok]
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
2 weeks, 3 days
Vous avez (1) nouveau message Apple-ID.
by iTunes
Chèr(e) client(e),
Nous vous informe que votre compte arrive à expiration dans moins 48
heures, il es impératif d'effectuer une vérification de vos informations des à
présent, sans quoi votre compte sera détruit. Cliquez simplement sur le lien ci-
dessous et ouvrez un session à l'aide de votre Apple ID et de votre mot de passe. Vérifiez maintenant
Pourquoi ce courrier électronique vous a-t-il été envoyé ?
L'envoi de ce courrier électronique s'applique lorsque la date d'expiration de votre
compte arrive à terme.
Pour plus d'informations, consultez la rubrique Questions et réponses.
Merci,
L'assistance à la clientèle Apple
TM and copyright © 2013 Apple Inc. 1 Infinite Loop, MS 96-DM, Cupertino, CA 95014. Alle Rechte vorbehalten / Informationsservice / Datenschutz / Meine Apple ID
12 years, 2 months
Should we build JBT 4.2 with JDK 7?
by Nick Boldt
Three of the projects in JBoss Tools use JDK 7 for testing: Server,
Webservices, and now Forge 2.
This is accomplished in Jenkins like this:
<jvmOptions>-Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m
-Djbosstools.test.jre.5="${NATIVE_TOOLS}${SEP}${JAVA15}"
-Djbosstools.test.jre.6="${NATIVE_TOOLS}${SEP}${JAVA16}"
-Djbosstools.test.jre.7="${NATIVE_TOOLS}${SEP}${JAVA17}"</jvmOptions>
But all the projects still use JDK 6 to compile.
<jdk>java16_default</jdk>
Is that OK? Or is it time to consider moving to JDK 7 for building as
well as running tests?
If this warrants a JIRA, please open one and link to it from here. If
not, discuss why it makes sense to stay with JDK 6 for compilation.
If your project needs JDK 7 to run tests, and is not listed above,
please open a JIRA or fix your _42 and _master jobs directly. If you
can't fix your job (not sure how or don't have permission), email me or
JIRA me and I'll fix your jobs for you.
Cheers,
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
12 years, 2 months