[JBoss JIRA] (JBIDE-26742) Create RedDeer methods for working with submodules of a module (module of a project deployed to server)
by Jeff MAURY (Jira)
[ https://issues.redhat.com/browse/JBIDE-26742?page=com.atlassian.jira.plug... ]
Jeff MAURY updated JBIDE-26742:
-------------------------------
Sprint: devex #172 Sep 2019, devex #173 Oct 2019, devex #176 Nov/Dec 2019, devex #177 Dec 2019, devex #178 Jan 2020, devex #179 Jan/Feb 2020 (was: devex #172 Sep 2019, devex #173 Oct 2019, devex #176 Nov/Dec 2019, devex #177 Dec 2019, devex #178 Jan 2020)
> Create RedDeer methods for working with submodules of a module (module of a project deployed to server)
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26742
> URL: https://issues.redhat.com/browse/JBIDE-26742
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.13.0.AM1
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
> Fix For: 4.14.0.AM1
>
> Attachments: The Servers view.png
>
>
> Methods has to work using the "Servers" view in the Red Hat CodeReady Studio.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (JBIDE-27006) Several maven.itests tests fail sporadically due to timeouts (missing wait statement or short time period)
by Jeff MAURY (Jira)
[ https://issues.redhat.com/browse/JBIDE-27006?page=com.atlassian.jira.plug... ]
Jeff MAURY updated JBIDE-27006:
-------------------------------
Sprint: devex #178 Jan 2020, devex #179 Jan/Feb 2020 (was: devex #178 Jan 2020)
> Several maven.itests tests fail sporadically due to timeouts (missing wait statement or short time period)
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-27006
> URL: https://issues.redhat.com/browse/JBIDE-27006
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.14.0.AM1
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Minor
> Fix For: 4.14.0.AM1
>
> Attachments: org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.testCompilerArguments.png, org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.testProcessorCustomOutput.png, org.jboss.tools.maven.ui.bot.test.configurator.CDIConfiguratorTest.testCDIConfiguratorEjbSeamInternational.png, org.jboss.tools.maven.ui.bot.test.configurator.JSFConfiguratorTest.testJSFConfigurator.png, org.jboss.tools.maven.ui.bot.test.conversion.MavenConversionTest.changeIdentifiedDependency.png
>
>
> h2. List and description of found and fixed issues:
> * *The hasNature() issue* - tests are calling the *hasNature()* method in *AbstractMavenSWTBotTest* abstract class, where a wait condition is missing. While working with the Project facets a popup window with progress bar sometimes show up. During testing it has shown up, that 10 seconds is not enought -> I am putting there 60 seconds
> !org.jboss.tools.maven.ui.bot.test.configurator.JSFConfiguratorTest.testJSFConfigurator.png|thumbnail!
> * *The createEJBProject() issue* - wait statement with too short period of time :
> !org.jboss.tools.maven.ui.bot.test.configurator.CDIConfiguratorTest.testCDIConfiguratorEjbSeamInternational.png|thumbnail!
> * *The createWebProject() issue* - wait statement with too short period of time :
> !org.jboss.tools.maven.ui.bot.test.conversion.MavenConversionTest.changeIdentifiedDependency.png|thumbnail!
> * *The createBasicMavenProject() issue* - wait statement with too short period of time
> !org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.testCompilerArguments.png|thumbnail!
> * *The prepareProject() issue* - wait statement with too short period of time
> !org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.testProcessorCustomOutput.png|thumbnail!
> * *The testAddRepositoryLinkInConversionWizard() issue* - wait statement with too short period of time
> * *The convertToMavenProject() issue* - wait statement with too short period of time
> * *The testMaterializeLibrary() issue* - wait statement with too short period of time
> * *The createJSFProject() issue* - wait statement with too short period of time
> h2. See the hasNature() issue stacktrace:
> {code:java}
> org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 10 s.: window is available
> at org.eclipse.reddeer.jface.preference.PreferenceDialog.ok(PreferenceDialog.java:119)
> at org.jboss.tools.maven.ui.bot.test.AbstractMavenSWTBotTest.hasNature(AbstractMavenSWTBotTest.java:117)
> at org.jboss.tools.maven.ui.bot.test.configurator.AbstractConfiguratorsTest.checkProjectWithRuntime(AbstractConfiguratorsTest.java:94)
> at org.jboss.tools.maven.ui.bot.test.configurator.JSFConfiguratorTest.testJSFConfigurator(JSFConfiguratorTest.java:82)
> {code}
> h2. See the createEJBProject() issue stacktrace:
> {code:java}
> org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: The following jobs are still running:
> Validating testEJB_CDI
> at org.jboss.tools.maven.ui.bot.test.configurator.AbstractConfiguratorsTest.createEJBProject(AbstractConfiguratorsTest.java:109)
> at org.jboss.tools.maven.ui.bot.test.configurator.CDIConfiguratorTest.testCDIConfiguratorEjbSeamInternational(CDIConfiguratorTest.java:123)
> {code}
> h2. See the createWebProject() issue stacktrace:
> {code:java}
> org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: The following jobs are still running:
> loading https://maven.apache.org/xsd/maven-4.0.0.xsd
> org.jboss.tools.maven.ui.bot.test.AbstractMavenSWTBotTest.createWebProject(AbstractMavenSWTBotTest.java:280)
> at org.jboss.tools.maven.ui.bot.test.conversion.MavenConversionTest.createWithRuntime(MavenConversionTest.java:204)
> at org.jboss.tools.maven.ui.bot.test.conversion.MavenConversionTest.changeIdentifiedDependency(MavenConversionTest.java:123)
> {code}
> h2. See the createBasicMavenProject() issue stackstrace:
> {code:java}
> org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 10 s.: The following jobs are still running:
> Validating test
> at org.eclipse.reddeer.eclipse.core.resources.AbstractResource.open(AbstractResource.java:78)
> at org.jboss.tools.maven.ui.bot.test.AbstractMavenSWTBotTest.openPom(AbstractMavenSWTBotTest.java:331)
> at org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.setCompilerArguments(APTPropertiesPageTest.java:298)
> at org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.testCompilerArguments(APTPropertiesPageTest.java:128)
> {code}
> h2. See the prepareProject() issue stackstrace:
> {code:java}
> org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 10 s.: The following jobs are still running:
> Validating test
> at org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.prepareProject(APTPropertiesPageTest.java:410)
> at org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.testProcessorCustomOutput(APTPropertiesPageTest.java:192)
> {code}
> h2. See the testAddRepositoryLinkInConversionWizard() issue stackstrace:
> {code:java}
> org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: The following jobs are still running:
> Validating WebProject
> at org.jboss.tools.maven.ui.bot.test.conversion.MavenConversionTest.testAddRepositoryLinkInConversionWizard(MavenConversionTest.java:172)
> {code}
> h2. See the convertToMavenProject() issue stackstrace:
> {code:java}
> at org.eclipse.reddeer.common.wait.WaitWhile.throwWaitTimeOutException(WaitWhile.java:116)
> at org.jboss.tools.maven.ui.bot.test.AbstractMavenSWTBotTest.convertToMavenProject(AbstractMavenSWTBotTest.java:241)
> at org.jboss.tools.maven.ui.bot.test.configurator.JSFConfiguratorTest.testJSFConfigurator(JSFConfiguratorTest.java:81)
> {code}
> h2. See the testMaterializeLibrary() issue stackstrace:
> {code:java}
> org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: The following jobs are still running:
> Validating example
> at org.jboss.tools.maven.ui.bot.test.conversion.MaterializeLibraryTest.testMaterializeLibrary(MaterializeLibraryTest.java:86)
> {code}
> h2. See the createJSFProject() issue stackstrace:
> {code:java}
> org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException:
> Timeout after: 60 s.: The following jobs are still running:
> Launching JSFProject7_1.2
> Validating JSFProject7_1.2
> at org.jboss.tools.maven.ui.bot.test.project.JSFProjectTest.createJSFProject(JSFProjectTest.java:72)
> at org.jboss.tools.maven.ui.bot.test.project.JSFProjectTest.createJSFProjectTest_AS7_JSFv2(JSFProjectTest.java:46)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (JBDS-4805) Error With Reccommenders: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct at org.eclipse.recommenders.internal.rcp.RcpModule$Listener$1.afterInjection(RcpModule.java:278)
by Jeff MAURY (Jira)
[ https://issues.redhat.com/browse/JBDS-4805?page=com.atlassian.jira.plugin... ]
Jeff MAURY updated JBDS-4805:
-----------------------------
Sprint: devex #178 Jan 2020, devex #179 Jan/Feb 2020 (was: devex #178 Jan 2020)
> Error With Reccommenders: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct at org.eclipse.recommenders.internal.rcp.RcpModule$Listener$1.afterInjection(RcpModule.java:278)
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4805
> URL: https://issues.redhat.com/browse/JBDS-4805
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 12.12.0.GA
> Environment: * eclipse.buildId=12.12.0.GA-v20190628-0434-B4598
> java.version=11.0.3-redhat
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -application org.eclipse.ui.ide.workbench -product com.jboss.devstudio.core.product
> Command-line arguments: -os win32 -ws win32 -arch x86_64 -application org.eclipse.ui.ide.workbench -product com.jboss.devstudio.core.product
> * Camel Fuse development
> Reporter: David Guthrie
> Assignee: Stephane Bouchet
> Priority: Major
> Fix For: 12.x
>
>
> Customer:
> {quote}
> I did an upgrade on Code Ready Studio to 12.12
> and when I go from
> {code}
> public void configure() throws Exception {
> from("file:E:/inputFolder")
> .split().tokenize("\n")
> .to("jms:queue:javininusex");
> }
> {code}
> to
> {code}
> @Override
> public void configure() throws Exception {
> from("{{route.start}}")
> .split().tokenize("\n")
> .log("{{route.start}}")
> .to("{{route.end}}");
> }
> {code}
> it starts show an error on the {{xxxx}} lines. which then sometimes goes to a pop up window that says check the recommender faq at .... (now this won't pop up and I didn't get the address) that is an invalid page.
> {quote}
> Log error
> org.eclipse.recommenders.completion.rcp
> Error
> Fri Oct 18 13:53:29 PDT 2019
> Session processor ‘class org.eclipse.recommenders.internal.calls.rcp.CallCompletionSessionProcessor’ failed with exception.
> {code}
> java.lang.NoClassDefFoundError: javax/annotation/PostConstruct
> at org.eclipse.recommenders.internal.rcp.RcpModule$Listener$1.afterInjection(RcpModule.java:278)
> at com.google.inject.internal.MembersInjectorImpl.notifyListeners(MembersInjectorImpl.java:97)
> at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:95)
> at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
> at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
> at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
> at com.google.inject.Scopes$1$1.get(Scopes.java:65)
> at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
> at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:54)
> at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:38)
> at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:62)
> at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:84)
> at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
> at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:54)
> at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
> at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
> at com.google.inject.Scopes$1$1.get(Scopes.java:65)
> at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
> at com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
> at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1024)
> at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
> at org.eclipse.recommenders.internal.calls.rcp.CallCompletionSessionProcessor.findReceiverTypeAndModel(CallCompletionSessionProcessor.java:136)
> at org.eclipse.recommenders.internal.calls.rcp.CallCompletionSessionProcessor.startSession(CallCompletionSessionProcessor.java:111)
> at org.eclipse.recommenders.completion.rcp.processable.IntelligentCompletionProposalComputer.fireStartSession(IntelligentCompletionProposalComputer.java:305)
> at org.eclipse.recommenders.completion.rcp.processable.IntelligentCompletionProposalComputer.computeCompletionProposals(IntelligentCompletionProposalComputer.java:171)
> at org.eclipse.jdt.internal.ui.text.java.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:336)
> at org.eclipse.jdt.internal.ui.text.java.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:340)
> at org.eclipse.jdt.internal.ui.text.java.ContentAssistProcessor.collectProposals(ContentAssistProcessor.java:334)
> at org.eclipse.jdt.internal.ui.text.java.ContentAssistProcessor.computeCompletionProposals(ContentAssistProcessor.java:291)
> at org.eclipse.jface.text.contentassist.ContentAssistant$2.lambda$0(ContentAssistant.java:2014)
> at java.base/java.util.Collections$SingletonSet.forEach(Collections.java:4795)
> at org.eclipse.jface.text.contentassist.ContentAssistant$2.run(ContentAssistant.java:2013)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
> at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:2010)
> at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:575)
> at org.eclipse.jface.text.contentassist.CompletionProposalPopup.lambda$0(CompletionProposalPopup.java:505)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:72)
> at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:500)
> at org.eclipse.jface.text.contentassist.ContentAssistant$AutoAssistListener.lambda$0(ContentAssistant.java:380)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3919)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3550)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:635)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:559)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:660)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:597)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1468)
> {code}
> This seems to be related to upstream issues https://bugs.eclipse.org/bugs/show_bug.cgi?id=541266 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=542689 where recommenders doesn't work with Java 11 and has been removed by upstream eclipse and by the Red Hat Eclipse RPM packages https://issues.jboss.org/browse/RHECLIPSE-82.
> I don't see a way to disable recommenders in codeready studio.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (JBIDE-23567) Integration tests global refactoring
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-23567?page=com.atlassian.jira.plug... ]
Josef Kopriva reassigned JBIDE-23567:
-------------------------------------
Assignee: Josef Kopriva (was: Pavol Srna)
> Integration tests global refactoring
> ------------------------------------
>
> Key: JBIDE-23567
> URL: https://issues.redhat.com/browse/JBIDE-23567
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests
> Reporter: Jeff MAURY
> Assignee: Josef Kopriva
> Priority: Major
> Labels: integration-test, integration_tests
> Fix For: 4.14.x
>
>
> We should done some work on integration tests so that we can rely on them to improve our code quality and reduce the technical debt.
> A sprint will be dedicated.
> Here are the tasks we should work on:
> * run tests from Maven and document how to run them if specific steps are required
> * If failure, fix the failed tests
> * Refactor / move tests to the components repository
> * Fix/make sure tests are run in PR check
> This huge task should be done component per component. Sub-tasks JIRA will be created for each component.
> You can use this document as a starting point:[https://docs.google.com/document/d/1bl8pJ2aW65UpyGpr3qxoAUREDWL26N...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (JBIDE-26887) Installing containers tools on RHEL 8.1
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-26887?page=com.atlassian.jira.plug... ]
Josef Kopriva commented on JBIDE-26887:
---------------------------------------
All container tools must be reviewed for all platforms.
> Installing containers tools on RHEL 8.1
> ---------------------------------------
>
> Key: JBIDE-26887
> URL: https://issues.redhat.com/browse/JBIDE-26887
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Affects Versions: 4.13.0.AM1
> Reporter: Zbyněk Červinka
> Assignee: Josef Kopriva
> Priority: Major
> Fix For: 4.14.0.Final
>
>
> *Info:*
> When provisioning scripts are running with labels "jbds docker" to provision RHEL 8+, the script automatically install podman instead docker (see the *label/rhel/docker.sh*). BUT THE SCRIPT IS STILL FAILING - IT NEEDS TO BE INVESTIGATED AND FIXED.
> *See the log with assert from Jenkins:*
> {code:java}
> [branch_rhel8-1-x64-jbds] Writing manifest to image destination
> [branch_rhel8-1-x64-jbds] Storing signatures
> [branch_rhel8-1-x64-jbds] 7b96db9590a8f5184871203f02f05e0160390edb1facd1bcf199e270815d037c
> [branch_rhel8-1-x64-jbds] Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
> [branch_rhel8-1-x64-jbds] 7b96db9590a8f5184871203f02f05e0160390edb1facd1bcf199e270815d037c
> [branch_rhel8-1-x64-jbds] test_talk_to_the_outer_world
> [branch_rhel8-1-x64-jbds] Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
> [branch_rhel8-1-x64-jbds] ASSERT:Unable to ping remote hosts from container: PING 10.38.5.26 (10.38.5.26) 56(84) bytes of data.
> [branch_rhel8-1-x64-jbds]
> [branch_rhel8-1-x64-jbds] --- 10.38.5.26 ping statistics ---
> [branch_rhel8-1-x64-jbds] 1 packets transmitted, 0 received, 100% packet loss, time 0ms
> [branch_rhel8-1-x64-jbds] Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
> [branch_rhel8-1-x64-jbds] c2c03a296d2329a4f3ab72a7bf38b78a8a80108204d326b0139d6af700e152d1
> [branch_rhel8-1-x64-jbds]
> [branch_rhel8-1-x64-jbds] Ran 4 tests.
> [branch_rhel8-1-x64-jbds]
> [branch_rhel8-1-x64-jbds] FAILED (failures=1)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (JBIDE-26887) Install containers tools on RHEL 8.1
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-26887?page=com.atlassian.jira.plug... ]
Josef Kopriva updated JBIDE-26887:
----------------------------------
Summary: Install containers tools on RHEL 8.1 (was: Installing containers tools on RHEL 8.1)
> Install containers tools on RHEL 8.1
> ------------------------------------
>
> Key: JBIDE-26887
> URL: https://issues.redhat.com/browse/JBIDE-26887
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Affects Versions: 4.13.0.AM1
> Reporter: Zbyněk Červinka
> Assignee: Josef Kopriva
> Priority: Major
> Fix For: 4.14.0.Final
>
>
> *Info:*
> When provisioning scripts are running with labels "jbds docker" to provision RHEL 8+, the script automatically install podman instead docker (see the *label/rhel/docker.sh*). BUT THE SCRIPT IS STILL FAILING - IT NEEDS TO BE INVESTIGATED AND FIXED.
> *See the log with assert from Jenkins:*
> {code:java}
> [branch_rhel8-1-x64-jbds] Writing manifest to image destination
> [branch_rhel8-1-x64-jbds] Storing signatures
> [branch_rhel8-1-x64-jbds] 7b96db9590a8f5184871203f02f05e0160390edb1facd1bcf199e270815d037c
> [branch_rhel8-1-x64-jbds] Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
> [branch_rhel8-1-x64-jbds] 7b96db9590a8f5184871203f02f05e0160390edb1facd1bcf199e270815d037c
> [branch_rhel8-1-x64-jbds] test_talk_to_the_outer_world
> [branch_rhel8-1-x64-jbds] Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
> [branch_rhel8-1-x64-jbds] ASSERT:Unable to ping remote hosts from container: PING 10.38.5.26 (10.38.5.26) 56(84) bytes of data.
> [branch_rhel8-1-x64-jbds]
> [branch_rhel8-1-x64-jbds] --- 10.38.5.26 ping statistics ---
> [branch_rhel8-1-x64-jbds] 1 packets transmitted, 0 received, 100% packet loss, time 0ms
> [branch_rhel8-1-x64-jbds] Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
> [branch_rhel8-1-x64-jbds] c2c03a296d2329a4f3ab72a7bf38b78a8a80108204d326b0139d6af700e152d1
> [branch_rhel8-1-x64-jbds]
> [branch_rhel8-1-x64-jbds] Ran 4 tests.
> [branch_rhel8-1-x64-jbds]
> [branch_rhel8-1-x64-jbds] FAILED (failures=1)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months