September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4687) StandaloneScriptTestCase fails on Eclipse OpenJ9

by James Perkins (Jira)

James Perkins created WFCORE-4687: ------------------------------------- Summary: StandaloneScriptTestCase fails on Eclipse OpenJ9 Key: WFCORE-4687 URL: https://issues.jboss.org/browse/WFCORE-4687 Project: WildFly Core Issue Type: Bug Components: Scripts Environment: java version "1.8.0_211" Java(TM) SE Runtime Environment (build 8.0.5.36 - pxa6480sr5fp36-20190510_01(SR5 FP36)) IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20190502_415899 (JIT enabled, AOT enabled) OpenJ9 - 46e57f9 OMR - 06a046a IBM - 0b909bf) JCL - 20190409_01 based on Oracle jdk8u211-b25 Reporter: Richard Opalka Assignee: James Perkins Fix For: 10.0.0.Beta6 [INFO] Running org.wildfly.scripts.test.StandaloneScriptTestCase [ERROR] Tests run: 10, Failures: 1, Errors: 0, Skipped: 8, Time elapsed: 20.724 s <<< FAILURE! - in org.wildfly.scripts.test.StandaloneScriptTestCase [ERROR] testBashScript[1](org.wildfly.scripts.test.StandaloneScriptTestCase) Time elapsed: 3.729 s <<< FAILURE! java.lang.AssertionError: Missing gc.log.0.current file in /home/opalka/git/redhat/wildfly-core/testsuite/scripts/target/wildfly-core/standalone/log at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.assertTrue(Assert.java:41) at org.wildfly.scripts.test.StandaloneScriptTestCase.testScript(StandaloneScriptTestCase.java:135) at org.wildfly.scripts.test.ScriptTestCase.executeTests(ScriptTestCase.java:257) at org.wildfly.scripts.test.ScriptTestCase.testBashScript(ScriptTestCase.java:170) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4687) StandaloneScriptTestCase fails on Eclipse OpenJ9

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4687?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4687: ---------------------------------- Environment: (was: java version "1.8.0_211" Java(TM) SE Runtime Environment (build 8.0.5.36 - pxa6480sr5fp36-20190510_01(SR5 FP36)) IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20190502_415899 (JIT enabled, AOT enabled) OpenJ9 - 46e57f9 OMR - 06a046a IBM - 0b909bf) JCL - 20190409_01 based on Oracle jdk8u211-b25 ) > StandaloneScriptTestCase fails on Eclipse OpenJ9 > ------------------------------------------------ > > Key: WFCORE-4687 > URL: https://issues.jboss.org/browse/WFCORE-4687 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Richard Opalka > Assignee: James Perkins > Priority: Major > > [INFO] Running org.wildfly.scripts.test.StandaloneScriptTestCase > [ERROR] Tests run: 10, Failures: 1, Errors: 0, Skipped: 8, Time elapsed: 20.724 s <<< FAILURE! - in org.wildfly.scripts.test.StandaloneScriptTestCase > [ERROR] testBashScript[1](org.wildfly.scripts.test.StandaloneScriptTestCase) Time elapsed: 3.729 s <<< FAILURE! > java.lang.AssertionError: Missing gc.log.0.current file in /home/opalka/git/redhat/wildfly-core/testsuite/scripts/target/wildfly-core/standalone/log > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.wildfly.scripts.test.StandaloneScriptTestCase.testScript(StandaloneScriptTestCase.java:135) > at org.wildfly.scripts.test.ScriptTestCase.executeTests(ScriptTestCase.java:257) > at org.wildfly.scripts.test.ScriptTestCase.testBashScript(ScriptTestCase.java:170) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4687) StandaloneScriptTestCase fails on Eclipse OpenJ9

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4687?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4687: ---------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly-core/pull/3928) > StandaloneScriptTestCase fails on Eclipse OpenJ9 > ------------------------------------------------ > > Key: WFCORE-4687 > URL: https://issues.jboss.org/browse/WFCORE-4687 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Richard Opalka > Assignee: James Perkins > Priority: Major > > [INFO] Running org.wildfly.scripts.test.StandaloneScriptTestCase > [ERROR] Tests run: 10, Failures: 1, Errors: 0, Skipped: 8, Time elapsed: 20.724 s <<< FAILURE! - in org.wildfly.scripts.test.StandaloneScriptTestCase > [ERROR] testBashScript[1](org.wildfly.scripts.test.StandaloneScriptTestCase) Time elapsed: 3.729 s <<< FAILURE! > java.lang.AssertionError: Missing gc.log.0.current file in /home/opalka/git/redhat/wildfly-core/testsuite/scripts/target/wildfly-core/standalone/log > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.wildfly.scripts.test.StandaloneScriptTestCase.testScript(StandaloneScriptTestCase.java:135) > at org.wildfly.scripts.test.ScriptTestCase.executeTests(ScriptTestCase.java:257) > at org.wildfly.scripts.test.ScriptTestCase.testBashScript(ScriptTestCase.java:170) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4687) StandaloneScriptTestCase fails on Eclipse OpenJ9

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4687?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4687: ---------------------------------- Fix Version/s: (was: 10.0.0.Beta6) > StandaloneScriptTestCase fails on Eclipse OpenJ9 > ------------------------------------------------ > > Key: WFCORE-4687 > URL: https://issues.jboss.org/browse/WFCORE-4687 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Richard Opalka > Assignee: James Perkins > Priority: Major > > [INFO] Running org.wildfly.scripts.test.StandaloneScriptTestCase > [ERROR] Tests run: 10, Failures: 1, Errors: 0, Skipped: 8, Time elapsed: 20.724 s <<< FAILURE! - in org.wildfly.scripts.test.StandaloneScriptTestCase > [ERROR] testBashScript[1](org.wildfly.scripts.test.StandaloneScriptTestCase) Time elapsed: 3.729 s <<< FAILURE! > java.lang.AssertionError: Missing gc.log.0.current file in /home/opalka/git/redhat/wildfly-core/testsuite/scripts/target/wildfly-core/standalone/log > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.wildfly.scripts.test.StandaloneScriptTestCase.testScript(StandaloneScriptTestCase.java:135) > at org.wildfly.scripts.test.ScriptTestCase.executeTests(ScriptTestCase.java:257) > at org.wildfly.scripts.test.ScriptTestCase.testBashScript(ScriptTestCase.java:170) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4686) Ensure the log manager is set for tests for Eclipse OpenJ9

by James Perkins (Jira)

James Perkins created WFCORE-4686: ------------------------------------- Summary: Ensure the log manager is set for tests for Eclipse OpenJ9 Key: WFCORE-4686 URL: https://issues.jboss.org/browse/WFCORE-4686 Project: WildFly Core Issue Type: Task Components: Logging Reporter: James Perkins Assignee: James Perkins WFCORE-3797 fixed the tests for the IBM J9 JVM. Since it's a different vendor name the tests should be fixed for Eclipse OpenJ9. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (HIBERNATE-169) provide better error log for BigDecimal when creating column failed

by nimo stephan (Jira)

nimo stephan created HIBERNATE-169: -------------------------------------- Summary: provide better error log for BigDecimal when creating column failed Key: HIBERNATE-169 URL: https://issues.jboss.org/browse/HIBERNATE-169 Project: Hibernate Integration Issue Type: Enhancement Reporter: nimo stephan Assignee: Steve Ebersole Steps to reproduce: Create a column {code:java} @Column(name = "price", precision = 7, scale = 10) private BigDecimal price; {code} and run the schema generation. Schema generation by Hibernate failed without pointing to the error. In this case the precision is lower than the scale, which is not right, hence the schema generation failed. Please provide better error logging, for example: {code:java} "Schema generation failed: field "price" the precision must be not lower than the scale" {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-217) Customizing settings.xml via ENV variables doesn't work on galleon image

by Jan Blizňák (Jira)

Jan Blizňák created WFWIP-217: --------------------------------- Summary: Customizing settings.xml via ENV variables doesn't work on galleon image Key: WFWIP-217 URL: https://issues.jboss.org/browse/WFWIP-217 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Jan Blizňák Assignee: Brian Stansberry With released images it is possible to configure settings.xml used for S2I build via ENV variables, eg: https://github.com/jboss-openshift/cct_module/blob/1ff1d96/jboss/containe... If I understood correctly this was introduced/changed by CLOUD-2911. But with galleon hooked into S2I the settings.xml is replaced with the one needed for slim server so this mechanism no longer works. This is a backward compatibility issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-216) Providing own ./configuration/settings.xml to S2I build doesn't work with galleon image

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFWIP-216?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated WFWIP-216: ------------------------------ Attachment: sti-custom-settings-standard-cd-image.log > Providing own ./configuration/settings.xml to S2I build doesn't work with galleon image > --------------------------------------------------------------------------------------- > > Key: WFWIP-216 > URL: https://issues.jboss.org/browse/WFWIP-216 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Brian Stansberry > Priority: Blocker > Attachments: sti-custom-settings-galleon-image.log, sti-custom-settings-standard-cd-image.log > > > According to https://access.redhat.com/documentation/en-us/red_hat_jboss_middleware_fo... the user is able to provide its own settings.xml located in <app_dir>/configuration/settings.xml - this settings file then should be used for mvn build. > This clearly conflicts with galleon settings.xml. However, this is broken backward compatibility and should be somehow addressed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-216) Providing own ./configuration/settings.xml to S2I build doesn't work with galleon image

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFWIP-216?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated WFWIP-216: ------------------------------ Attachment: sti-custom-settings-galleon-image.log > Providing own ./configuration/settings.xml to S2I build doesn't work with galleon image > --------------------------------------------------------------------------------------- > > Key: WFWIP-216 > URL: https://issues.jboss.org/browse/WFWIP-216 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Brian Stansberry > Priority: Blocker > Attachments: sti-custom-settings-galleon-image.log, sti-custom-settings-standard-cd-image.log > > > According to https://access.redhat.com/documentation/en-us/red_hat_jboss_middleware_fo... the user is able to provide its own settings.xml located in <app_dir>/configuration/settings.xml - this settings file then should be used for mvn build. > This clearly conflicts with galleon settings.xml. However, this is broken backward compatibility and should be somehow addressed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-216) Providing own ./configuration/settings.xml to S2I build doesn't work with galleon image

by Jan Blizňák (Jira)

Jan Blizňák created WFWIP-216: --------------------------------- Summary: Providing own ./configuration/settings.xml to S2I build doesn't work with galleon image Key: WFWIP-216 URL: https://issues.jboss.org/browse/WFWIP-216 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Jan Blizňák Assignee: Brian Stansberry According to https://access.redhat.com/documentation/en-us/red_hat_jboss_middleware_fo... the user is able to provide its own settings.xml located in <app_dir>/configuration/settings.xml - this settings file then should be used for mvn build. This clearly conflicts with galleon settings.xml. However, this is broken backward compatibility and should be somehow addressed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2019