August 2019 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-4183) Extend travis testing with elytron profile

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4183?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4183: ------------------------------ Git Pull Request: https://github.com/jbossws/jbossws-cxf/pull/112, https://github.com/jbossws/jbossws-cxf/pull/117 (was: https://github.com/jbossws/jbossws-cxf/pull/112) Additional PR with only part of the commits at https://github.com/jbossws/jbossws-cxf/pull/117, the previous PR will wait for the fix of the JBWS-4180 > Extend travis testing with elytron profile > ------------------------------------------ > > Key: JBWS-4183 > URL: https://issues.jboss.org/browse/JBWS-4183 > Project: JBoss Web Services > Issue Type: Task > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Major > > Currently the travis for jbossws-cxf is configured to test 3 most recent server integration with two jdks, also in combination with security manager enabled or not > (jdk8|jdk11) x (secmgr on|secmgr off) x (wildfly1600|wildfly1700|wildfly1800) > The problem is we are lacking test run with elytron security configuration which already caused we missed a regression JBWS-4180. > The other issue is that the security manager scenario as executed in travis is no different from standard run except one skipped test, causing half of running configuration to be redundant, this must be revisited if the test scenario is still desired. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4187) Allow to change default startup timeout when starting containers in TS

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4187?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4187: ------------------------------ Git Pull Request: https://github.com/jbossws/jbossws-cxf/pull/116 PR sent https://github.com/jbossws/jbossws-cxf/pull/116 > Allow to change default startup timeout when starting containers in TS > ---------------------------------------------------------------------- > > Key: JBWS-4187 > URL: https://issues.jboss.org/browse/JBWS-4187 > Project: JBoss Web Services > Issue Type: Task > Affects Versions: jbossws-cxf-5.3.0.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Minor > > Current setup for arquillian doesn't set {{startupTimeoutInSeconds}} property and as such it uses default 60s timeout for every container started during testsuite execution. > This is fine most of the time but when executing accross many platforms and JDK combinations in CI on heavily used machines it happens from time to time this timeout is not enough. It would be convinient to have the ability to set the timeout to the higher value form the command line. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4187) Allow to change default startup timeout when starting containers in TS

by Jan Blizňák (Jira)

Jan Blizňák created JBWS-4187: --------------------------------- Summary: Allow to change default startup timeout when starting containers in TS Key: JBWS-4187 URL: https://issues.jboss.org/browse/JBWS-4187 Project: JBoss Web Services Issue Type: Task Affects Versions: jbossws-cxf-5.3.0.Final Reporter: Jan Blizňák Assignee: Jan Blizňák Current setup for arquillian doesn't set {{startupTimeoutInSeconds}} property and as such it uses default 60s timeout for every container started during testsuite execution. This is fine most of the time but when executing accross many platforms and JDK combinations in CI on heavily used machines it happens from time to time this timeout is not enough. It would be convinient to have the ability to set the timeout to the higher value form the command line. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4186) Exclude SignEncryptGCMTestCase on IBM JDK8 due to JBEAP-5200

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4186?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4186: ------------------------------ Git Pull Request: https://github.com/jbossws/jbossws-cxf/pull/115 PR sent https://github.com/jbossws/jbossws-cxf/pull/115 > Exclude SignEncryptGCMTestCase on IBM JDK8 due to JBEAP-5200 > ------------------------------------------------------------ > > Key: JBWS-4186 > URL: https://issues.jboss.org/browse/JBWS-4186 > Project: JBoss Web Services > Issue Type: Task > Affects Versions: jbossws-cxf-5.3.0.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Major > > As JBEAP-5200 doesn't look it would ever be fixed, let's take a pragmatic approrach and ignore the tests when executed with IBM JDK8. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4186) Exclude SignEncryptGCMTestCase on IBM JDK8 due to JBEAP-5200

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4186?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4186: ------------------------------ Description: As JBEAP-5200 doesn't look it would ever be fixed, let's take a pragmatic approrach and ignore the tests when executed with IBM JDK8. (was: As JBEAP-5200 doesn't look it would ever be fixed, let's take a pragmatic approrach and ignore the tests when executed with such JDK.) > Exclude SignEncryptGCMTestCase on IBM JDK8 due to JBEAP-5200 > ------------------------------------------------------------ > > Key: JBWS-4186 > URL: https://issues.jboss.org/browse/JBWS-4186 > Project: JBoss Web Services > Issue Type: Task > Affects Versions: jbossws-cxf-5.3.0.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Major > > As JBEAP-5200 doesn't look it would ever be fixed, let's take a pragmatic approrach and ignore the tests when executed with IBM JDK8. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4186) Exclude SignEncryptGCMTestCase on IBM JDK8 due to JBEAP-5200

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4186?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4186: ------------------------------ Description: As JBEAP-5200 doesn't look it would ever be fixed, let's take a pragmatic approrach and ignore the tests when executed with such JDK. (was: As JBWS-5200 doesn't look it would ever be fixed, let's take a pragmatic approrach and ignore the tests when executed with such JDK.) > Exclude SignEncryptGCMTestCase on IBM JDK8 due to JBEAP-5200 > ------------------------------------------------------------ > > Key: JBWS-4186 > URL: https://issues.jboss.org/browse/JBWS-4186 > Project: JBoss Web Services > Issue Type: Task > Affects Versions: jbossws-cxf-5.3.0.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Major > > As JBEAP-5200 doesn't look it would ever be fixed, let's take a pragmatic approrach and ignore the tests when executed with such JDK. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4186) Exclude SignEncryptGCMTestCase on IBM JDK8 due to JBEAP-5200

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4186?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4186: ------------------------------ Summary: Exclude SignEncryptGCMTestCase on IBM JDK8 due to JBEAP-5200 (was: Exclude SignEncryptGCMTestCase on IBM JDK8 due to JBWS-5200) > Exclude SignEncryptGCMTestCase on IBM JDK8 due to JBEAP-5200 > ------------------------------------------------------------ > > Key: JBWS-4186 > URL: https://issues.jboss.org/browse/JBWS-4186 > Project: JBoss Web Services > Issue Type: Task > Affects Versions: jbossws-cxf-5.3.0.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Major > > As JBWS-5200 doesn't look it would ever be fixed, let's take a pragmatic approrach and ignore the tests when executed with such JDK. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4186) Exclude SignEncryptGCMTestCase on IBM JDK8 due to JBWS-5200

by Jan Blizňák (Jira)

Jan Blizňák created JBWS-4186: --------------------------------- Summary: Exclude SignEncryptGCMTestCase on IBM JDK8 due to JBWS-5200 Key: JBWS-4186 URL: https://issues.jboss.org/browse/JBWS-4186 Project: JBoss Web Services Issue Type: Task Affects Versions: jbossws-cxf-5.3.0.Final Reporter: Jan Blizňák Assignee: Jan Blizňák As JBWS-5200 doesn't look it would ever be fixed, let's take a pragmatic approrach and ignore the tests when executed with such JDK. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4185) IgnoreEnv and IgnoreContainer rules make false positives

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4185?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4185: ------------------------------ Git Pull Request: https://github.com/jbossws/jbossws-cxf/pull/114 PR sent https://github.com/jbossws/jbossws-cxf/pull/114 > IgnoreEnv and IgnoreContainer rules make false positives > -------------------------------------------------------- > > Key: JBWS-4185 > URL: https://issues.jboss.org/browse/JBWS-4185 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.3.0.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Major > > Current implementations of Ignore* test rules can only skip the test when theirs assume fails. However, when assume passes it will mark test as passed no matter what the real outcome would be. > The problem is the rule does not call the base {{Statement}} it is wrapped around so it effectively stops the execution of the test. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4185) IgnoreEnv and IgnoreContainer rules make false positives

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4185?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4185: ------------------------------ Summary: IgnoreEnv and IgnoreContainer rules make false positives (was: Ignore rules make false positives) > IgnoreEnv and IgnoreContainer rules make false positives > -------------------------------------------------------- > > Key: JBWS-4185 > URL: https://issues.jboss.org/browse/JBWS-4185 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.3.0.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Major > > Current implementations of Ignore* test rules can only skip the test when theirs assume fails. However, when assume passes it will mark test as passed no matter what the real outcome would be. > The problem is the rule does not call the base {{Statement}} it is wrapped around so it effectively stops the execution of the test. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues August 2019