ACTION REQUIRED: core Beta2 branch/codefreeze Thursday - steps inside
by Max Rydahl Andersen
Hi core-compnent leads,
Thursday 13th is branch/codefreeze day as planned [1].
Special Note:
Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
line of defense/attack on this codefreeze.
A quick reminder what branch/codefreeze means for each component/repo owner:
0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.
1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools parent.
Should look something like this:
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.0.Beta2-SNAPSHOT</version>
</parent>
2) Make sure your component builds and passes its tests when run locally.
$ mvn clean verify
3) Make a branch for the Beta2 builds to use.
Most components uses master, thus the steps would be something like:
$ git checkout master
$ git pull origin master
$ git checkout -b jbosstools-4.1.0.Beta2x
$ git push origin jbosstools-4.1.0.Beta2x
4) Respond to this mail before end of Thursday with a "All Done for component:
<your component>" or "<your component> cannot branch/freeze today because of
<jira issues> must be done first"
Thank you!
[1] https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
12 years, 8 months
ACTION REQUIRED for Server, Javaee, Central: failing tests in master branch / please fix for Beta2 code freeze
by Nick Boldt
The following projects are red in Jenkins due to test timeouts:
Server:
[INFO] org.jboss.ide.eclipse.archives.test ............... FAILURE [40:05.535s]
[ERROR] Failed to execute goal
org.eclipse.tycho:tycho-surefire-plugin:0.18.0:test (default-test) on
project org.jboss.ide.eclipse.archives.test: Error while executing
platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException:
Error while executing external command, process killed. Process
timeout out after 2400 seconds -> [Help 1]
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
Javaee:
19:02:51 [INFO] org.jboss.tools.jsf.ui.test .......................
FAILURE [1:00:15.201s]
19:02:52 [ERROR] Failed to execute goal
org.eclipse.tycho:tycho-surefire-plugin:0.18.0:test (default-test) on
project org.jboss.tools.jsf.ui.test: Error while executing platform:
org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while
executing external command, process killed. Process timeout out after
3600 seconds -> [Help 1]
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
Central:
[INFO] org.jboss.tools.maven.sourcelookup.test ........... FAILURE [40:17.222s]
[ERROR] Failed to execute goal
org.eclipse.tycho:tycho-surefire-plugin:0.18.0:test (default-test) on
project org.jboss.tools.maven.sourcelookup.test: Error while executing
platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException:
Error while executing external command, process killed. Process
timeout out after 2400 seconds -> [Help 1]
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
--
If your project is listed above, please open a JIRA against yourself
to track this problem. If your project is NOT listed, but you're
yellow due to test failures (or skipped tests)... please fix those
too!
--
Nick Boldt :: Productization Lead :: JBoss Tools & Dev Studio :: Red Hat, Inc.
http://nick.divbyzero.com
12 years, 8 months
Re: [jbosstools-dev] ACTION REQUIRED for Server, Javaee, Central: failing tests in master branch / please fix for Beta2 code freeze
by Victor Rubezhny
jbosstools-javaee has:
- known test failure in seam: https://issues.jboss.org/browse/JBIDE-14105
- a timed out test in JSF UI (JsfUiAllTests) - it occurs from time to
time on my environment (tonight it was reproduced)
Also, it looks like there still is a problem with Workbench Auto-Save
Job: The option -Dorg.eclipse.ui.testsDisableWorkbenchAutoSave=true that
is included into command line is not respected by Eclipse RC3 for some
reason or works not as expected.
Even having such option in the command line we still have this
never-ending job running:
Regards,
Victor
On 06/13/2013 02:22 AM, Denis Golovin wrote:
> On 06/12/2013 03:18 PM, Denis Golovin wrote:
>> On 06/12/2013 12:54 PM, Nick Boldt wrote:
>>> The following projects are red in Jenkins due to test timeouts:
>>>
>>> Server:
>>>
>>> [INFO] org.jboss.ide.eclipse.archives.test ............... FAILURE [40:05.535s]
>>> [ERROR] Failed to execute goal
>>> org.eclipse.tycho:tycho-surefire-plugin:0.18.0:test (default-test) on
>>> project org.jboss.ide.eclipse.archives.test: Error while executing
>>> platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException:
>>> Error while executing external command, process killed. Process
>>> timeout out after 2400 seconds -> [Help 1]
>>>
>>> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
>> Changed configuration to use XVnc and that helped. But results look
>> weird. In log
>> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
>> is says for severl test plugins
>>
>> [ERROR] There are test failures.
>>
>>
>> but in the end it shows
>>
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] archives.tests .................................... SUCCESS [0.393s]
>> [INFO] org.jboss.ide.eclipse.archives.test ............... SUCCESS [50.395s]
>> [INFO] org.jboss.ide.eclipse.archives.ui.test ............ SUCCESS [15.450s]
>> [INFO] jmx.tests ......................................... SUCCESS [0.005s]
>> [INFO] org.jboss.tools.jmx.core.test ..................... SUCCESS [21.032s]
>> [INFO] as.tests .......................................... SUCCESS [0.005s]
>> [INFO] org.jboss.tools.as.test.core ...................... SUCCESS [11:46.553s]
>> [INFO] org.jboss.ide.eclipse.as.archives.integration.test SUCCESS [1:04.715s]
>> [INFO] org.jboss.ide.eclipse.as.management.as7.tests ..... SUCCESS [3:49.784s]
>> [INFO] org.jboss.ide.eclipse.as.test ..................... SUCCESS [17.708s]
>> [INFO] org.jboss.ide.eclipse.as.ui.test .................. SUCCESS [25.602s]
>> [INFO] org.jboss.tools.jmx.ui.test ....................... SUCCESS [6.418s]
>> [INFO] server.all.tests .................................. SUCCESS [0.004s]
>> [INFO] ------------------------------------------------------------------------
>>
>> And build marked as unstable.
>>
>>
>>> Javaee:
>>>
>>> 19:02:51 [INFO] org.jboss.tools.jsf.ui.test .......................
>>> FAILURE [1:00:15.201s]
>>>
>>> 19:02:52 [ERROR] Failed to execute goal
>>> org.eclipse.tycho:tycho-surefire-plugin:0.18.0:test (default-test) on
>>> project org.jboss.tools.jsf.ui.test: Error while executing platform:
>>> org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while
>>> executing external command, process killed. Process timeout out after
>>> 3600 seconds -> [Help 1]
>>>
>>> http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
>>
>> Back to be running again, but seems to have test errors
>>
>> [ERROR] There are test failures.
>
> The same problem with reactor summary as in server. There are test
> failures but reactor summary says everything was build successfully.
> Does it smell like tycho 0.18.0 issue?
>
>
>>
>>
>>> Central:
>>>
>>> [INFO] org.jboss.tools.maven.sourcelookup.test ........... FAILURE [40:17.222s]
>>>
>>> [ERROR] Failed to execute goal
>>> org.eclipse.tycho:tycho-surefire-plugin:0.18.0:test (default-test) on
>>> project org.jboss.tools.maven.sourcelookup.test: Error while executing
>>> platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException:
>>> Error while executing external command, process killed. Process
>>> timeout out after 2400 seconds -> [Help 1]
>>>
>>> http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
>>
>> Configured to use Xvnc and seems to be all blue again.
>>
>> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
>>
>>> --
>>>
>>> If your project is listed above, please open a JIRA against yourself
>>> to track this problem. If your project is NOT listed, but you're
>>> yellow due to test failures (or skipped tests)... please fix those
>>> too!
>>>
>>
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
12 years, 8 months
Upcoming changes in Target Platform: Kepler RC3
by Mickael Istria
Hi all,
I'll start the process of updating target platform to Kepler RC3 to spot
some potential changes in Kepler that could affect us. This should also
help to fix JBIDE-13989 (by the way, is there an automated test that
reproduce this issue so we can make sure moving to Kepler fixes it?).
If you have some specific requirements out of this move to Kepler RC3,
please open Jiras right now.
The version of target platform won't change and will remain
4.30.5.Alpha6-SNAPSHOT for now.
First, I'm going to mirror the newer sites of our dependencies.
Then I'll propose a PR for review (mainly by Nick if he finds time at
JUDCon), it's the right rime for you to have a look if you're curious
about some changes in your dependencies.
Hopefully, I'll be allowed to merge it soon, so we'll get feedback from
CI early enough to spot issues before we branch.
Cheers.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
12 years, 8 months
URGENT: Please update reference parent pom to 4.1.0.Beta2-SNAPSHOT
by Mickael Istria
Hi all,
Many components still reference parent pom 4.1.0.Beta1-SNAPSHOT which
reference the repositories for JBT 4.1.0.Beta1. Some refactoring in the
jbosstools-base component have happened recently (renaming of httpclient
bundle, introduction of the "foundation" module) and it is important
that you build against these changes.
In order to do so, you NEED TO change reference to parent pom in your
component to use 4.1.0.Beta2-SNAPSHOT AS SOON AS POSSIBLE. This will
make CI bluer and overall quality better.
From a build maintenance POV, this shows we have to think of a better
way to handle how we reference repositories in parent pom and how we
should not change those URLs. Brainstorming in progress....
Cheers,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
12 years, 9 months
