[JBoss JIRA] (JBIDE-21310) 0 Test Failure(s) in JBIDE 4.3.1.Beta1 for seam2 component
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21310?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21310:
-------------------------------
Attachment: seamxmltext.log.txt
This is probably a sporadic/intermittent test failure, but since it's happening after code freeze, I figured I'd log it.
Here's the console log from http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...:
[^seamxmltext.log.txt]
build console had nothing terribly helpful:
{code}
23:40:04 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.24.0:test (default-test) on project org.jboss.tools.seam.ui.test: An unexpected error occured while launching the test runtime (return code 143). See log for details. -> [Help 1]
23:40:04 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.24.0:test (default-test) on project org.jboss.tools.seam.ui.test: An unexpected error occured while launching the test runtime (return code 143). See log for details.
23:40:04 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
23:40:04 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
23:40:04 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
23:40:04 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
23:40:04 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
23:40:04 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
23:40:04 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
23:40:04 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
23:40:04 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
23:40:04 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
23:40:04 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
23:40:04 at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
23:40:04 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
23:40:04 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
23:40:04 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
23:40:04 at java.lang.reflect.Method.invoke(Method.java:497)
23:40:04 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
23:40:04 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
23:40:04 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
23:40:04 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
23:40:04 Caused by: org.apache.maven.plugin.MojoFailureException: An unexpected error occured while launching the test runtime (return code 143). See log for details.
23:40:04 at org.eclipse.tycho.surefire.TestMojo.runTest(TestMojo.java:958)
23:40:04 at org.eclipse.tycho.surefire.TestMojo.execute(TestMojo.java:630)
23:40:04 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
23:40:04 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
23:40:04 ... 19 more{code}
> 0 Test Failure(s) in JBIDE 4.3.1.Beta1 for seam2 component
> ----------------------------------------------------------
>
> Key: JBIDE-21310
> URL: https://issues.jboss.org/browse/JBIDE-21310
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: seam2
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Priority: Critical
> Labels: testfailure
> Attachments: seamxmltext.log.txt
>
>
> *0 Test Failure(s) in JBIDE 4.3.1.Beta1 for seam2 component:*
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_4.3...
> [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for seam2 component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
> -----
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBDS-3550) Developer - autodetect the CDK in IDE
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBDS-3550?page=com.atlassian.jira.plugin.... ]
Rob Stryker closed JBDS-3550.
-----------------------------
Resolution: Done
the last pieces have been added. Remaining work is small UI stuff / fixes to either workflow / credential ui / other. New issues will be opened for it.
> Developer - autodetect the CDK in IDE
> -------------------------------------
>
> Key: JBDS-3550
> URL: https://issues.jboss.org/browse/JBDS-3550
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: runtime-detection
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Fix For: 9.1.0.Beta1, 10.0.0.Alpha1
>
>
> User Story:
> As a Developer on first startup after the installer have run, the CDK should be configured in the IDE and be ready to use
> Acceptance Criteria:
> * If the CDK is running there should be an openshift connection that is configured with the right url and username and users should have been given a password that allows him to connect
> * if the CDK is running there should be a docker connection that is configured with the right connetion info, certifcates etc. to connect
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-19974) Cannot detect running boot2docker on OS X
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19974?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19974:
------------------------------------
Patches committed to upstream docker and built today, then released and mirrored to http://download.jboss.org/jbosstools/updates/requirements/docker/1.2.0.20... as part of JBIDE-21305.
Therefore resolving this issue so QE can verify.
> Cannot detect running boot2docker on OS X
> -----------------------------------------
>
> Key: JBIDE-19974
> URL: https://issues.jboss.org/browse/JBIDE-19974
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, upstream
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Assignee: Xavier Coulon
> Fix For: 4.3.1.Beta1
>
>
> In Docker Explorer, when I want to create my first connection, I click on the link to create a connection, the dialog is opened and I get this in my Error View:
> bash: no job control in this shell
> An exception stack trace is not available.
> Another warning is generated also:
> Could not find default settings to connect to a local Docker daemon
> An exception stack trace is not available.
> I'm on OS X and have boot2docker running. By default, boot2docker will not add the DOCKER variables to .bash_profile, it will only instruct me to set them up like this:
> export DOCKER_HOST=tcp://192.168.59.103:2376
> export DOCKER_CERT_PATH=/Users/rasp/.boot2docker/certs/boot2docker-vm
> export DOCKER_TLS_VERIFY=1
> With the way the script in the Docker Tooling works (env | grep DOCKER), it cannot detect the variables unless they are in .bash_profile.
> But even if I added them there (and a new Terminal window has these variables), Eclipse still can't detect the running Docker instance.
> So something is wrong.
> I logged an upstream bug here:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=469624
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-19974) Cannot detect running boot2docker on OS X
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19974?page=com.atlassian.jira.plugi... ]
Nick Boldt resolved JBIDE-19974.
--------------------------------
Resolution: Done
> Cannot detect running boot2docker on OS X
> -----------------------------------------
>
> Key: JBIDE-19974
> URL: https://issues.jboss.org/browse/JBIDE-19974
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, upstream
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Assignee: Xavier Coulon
> Fix For: 4.3.1.Beta1
>
>
> In Docker Explorer, when I want to create my first connection, I click on the link to create a connection, the dialog is opened and I get this in my Error View:
> bash: no job control in this shell
> An exception stack trace is not available.
> Another warning is generated also:
> Could not find default settings to connect to a local Docker daemon
> An exception stack trace is not available.
> I'm on OS X and have boot2docker running. By default, boot2docker will not add the DOCKER variables to .bash_profile, it will only instruct me to set them up like this:
> export DOCKER_HOST=tcp://192.168.59.103:2376
> export DOCKER_CERT_PATH=/Users/rasp/.boot2docker/certs/boot2docker-vm
> export DOCKER_TLS_VERIFY=1
> With the way the script in the Docker Tooling works (env | grep DOCKER), it cannot detect the variables unless they are in .bash_profile.
> But even if I added them there (and a new Terminal window has these variables), Eclipse still can't detect the running Docker instance.
> So something is wrong.
> I logged an upstream bug here:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=469624
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months