From issues at jboss.org Fri Dec 2 03:54:01 2016 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Fri, 2 Dec 2016 03:54:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1868) JVM waits for Spacelift's cached threads to timeout causing its termination delay In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reassigned ARQ-1868: -------------------------------- Assignee: (was: Karel Piwko) > JVM waits for Spacelift's cached threads to timeout causing its termination delay > --------------------------------------------------------------------------------- > > Key: ARQ-1868 > URL: https://issues.jboss.org/browse/ARQ-1868 > Project: Arquillian > Issue Type: Bug > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Attachments: spacelift_thread_dump.txt > > > In the current implementation of ExecutorService there is this constructor:; > {code} > public ExecutionServiceImpl() { > this.service = Executors.newCachedThreadPool(); > this.scheduledService = Executors.newScheduledThreadPool(1); > } > {code} > JavaDoc for cachedThreadPool says: > {quote} > Threads that have not been used for sixty seconds are terminated and removed from the cache. Thus, a pool that remains idle for long enough will not consume any resources. > {quote} > While this is indeed useful, it seems that even JVM has nothing to do, it waits for these cached threads to timeout (so they are not used some time (60 seconds by default) so they are destroyed eventually) and only after their destruction whole JVM terminates properly. > Please consider to lower the timeout so user does not have to wait or figure out other pooling mechanism. > This issue effects mainly command line tools which hangs without obvious reason and debugging it why is a nightmare. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Dec 2 03:55:00 2016 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Fri, 2 Dec 2016 03:55:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1868) JVM waits for Spacelift's cached threads to timeout causing its termination delay In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13332821#comment-13332821 ] Karel Piwko commented on ARQ-1868: ---------------------------------- [~mjobanek] [~smikloso] do we still need this issue to be fixed? Otherwise I suggest to close it as won't fix / out of date. > JVM waits for Spacelift's cached threads to timeout causing its termination delay > --------------------------------------------------------------------------------- > > Key: ARQ-1868 > URL: https://issues.jboss.org/browse/ARQ-1868 > Project: Arquillian > Issue Type: Bug > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Attachments: spacelift_thread_dump.txt > > > In the current implementation of ExecutorService there is this constructor:; > {code} > public ExecutionServiceImpl() { > this.service = Executors.newCachedThreadPool(); > this.scheduledService = Executors.newScheduledThreadPool(1); > } > {code} > JavaDoc for cachedThreadPool says: > {quote} > Threads that have not been used for sixty seconds are terminated and removed from the cache. Thus, a pool that remains idle for long enough will not consume any resources. > {quote} > While this is indeed useful, it seems that even JVM has nothing to do, it waits for these cached threads to timeout (so they are not used some time (60 seconds by default) so they are destroyed eventually) and only after their destruction whole JVM terminates properly. > Please consider to lower the timeout so user does not have to wait or figure out other pooling mechanism. > This issue effects mainly command line tools which hangs without obvious reason and debugging it why is a nightmare. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Dec 5 08:01:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 5 Dec 2016 08:01:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1868) JVM waits for Spacelift's cached threads to timeout causing its termination delay In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13333856#comment-13333856 ] Matous Jobanek commented on ARQ-1868: ------------------------------------- Hi, to be honest, I haven't faced this issue in any project (where Spacelift is used) yet; so from my point of view it can be closed. > JVM waits for Spacelift's cached threads to timeout causing its termination delay > --------------------------------------------------------------------------------- > > Key: ARQ-1868 > URL: https://issues.jboss.org/browse/ARQ-1868 > Project: Arquillian > Issue Type: Bug > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Attachments: spacelift_thread_dump.txt > > > In the current implementation of ExecutorService there is this constructor:; > {code} > public ExecutionServiceImpl() { > this.service = Executors.newCachedThreadPool(); > this.scheduledService = Executors.newScheduledThreadPool(1); > } > {code} > JavaDoc for cachedThreadPool says: > {quote} > Threads that have not been used for sixty seconds are terminated and removed from the cache. Thus, a pool that remains idle for long enough will not consume any resources. > {quote} > While this is indeed useful, it seems that even JVM has nothing to do, it waits for these cached threads to timeout (so they are not used some time (60 seconds by default) so they are destroyed eventually) and only after their destruction whole JVM terminates properly. > Please consider to lower the timeout so user does not have to wait or figure out other pooling mechanism. > This issue effects mainly command line tools which hangs without obvious reason and debugging it why is a nightmare. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Dec 7 07:12:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 7 Dec 2016 07:12:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2061) Upgrade to Selenium 3 In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2061: ----------------------------------- Summary: Upgrade to Selenium 3 Key: ARQ-2061 URL: https://issues.jboss.org/browse/ARQ-2061 Project: Arquillian Issue Type: Component Upgrade Components: Extension - Drone Affects Versions: drone_2.0.1.Final Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_3.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Dec 7 07:14:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 7 Dec 2016 07:14:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2062) Upgrade jboss-parent to latest version (21) In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2062: ----------------------------------- Summary: Upgrade jboss-parent to latest version (21) Key: ARQ-2062 URL: https://issues.jboss.org/browse/ARQ-2062 Project: Arquillian Issue Type: Component Upgrade Components: Extension - Drone Affects Versions: drone_2.0.1.Final Reporter: Matous Jobanek Assignee: Matous Jobanek -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Dec 7 07:15:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 7 Dec 2016 07:15:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2063) Upgrade build.gradle file to use Spacelift 17 and Gradle 2.5 In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2063: ----------------------------------- Summary: Upgrade build.gradle file to use Spacelift 17 and Gradle 2.5 Key: ARQ-2063 URL: https://issues.jboss.org/browse/ARQ-2063 Project: Arquillian Issue Type: Component Upgrade Components: Extension - Drone Affects Versions: drone_2.0.1.Final Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_3.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Dec 7 07:16:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 7 Dec 2016 07:16:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2062) Upgrade jboss-parent to latest version (21) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2062: -------------------------------- Fix Version/s: drone_3.0.0.Alpha1 > Upgrade jboss-parent to latest version (21) > ------------------------------------------- > > Key: ARQ-2062 > URL: https://issues.jboss.org/browse/ARQ-2062 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.0.1.Final > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_3.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Dec 7 10:14:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 7 Dec 2016 10:14:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2064) Upgrade JUnit to 4.12 In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2064: ----------------------------------- Summary: Upgrade JUnit to 4.12 Key: ARQ-2064 URL: https://issues.jboss.org/browse/ARQ-2064 Project: Arquillian Issue Type: Component Upgrade Components: Extension - Drone Affects Versions: drone_2.0.1.Final Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_3.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Dec 9 10:55:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 9 Dec 2016 10:55:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2063) Upgrade build.gradle file to use Spacelift 17 and Gradle 2.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2063: -------------------------------- Fix Version/s: drone_2.1.0.Alpha1 > Upgrade build.gradle file to use Spacelift 17 and Gradle 2.5 > ------------------------------------------------------------ > > Key: ARQ-2063 > URL: https://issues.jboss.org/browse/ARQ-2063 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.0.1.Final > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_3.0.0.Alpha1, drone_2.1.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Dec 9 10:56:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 9 Dec 2016 10:56:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2062) Upgrade jboss-parent to latest version (21) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2062: -------------------------------- Fix Version/s: drone_2.1.0.Alpha1 > Upgrade jboss-parent to latest version (21) > ------------------------------------------- > > Key: ARQ-2062 > URL: https://issues.jboss.org/browse/ARQ-2062 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.0.1.Final > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_3.0.0.Alpha1, drone_2.1.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Dec 9 10:56:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 9 Dec 2016 10:56:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2064) Upgrade JUnit to 4.12 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2064: -------------------------------- Fix Version/s: drone_2.1.0.Alpha1 > Upgrade JUnit to 4.12 > --------------------- > > Key: ARQ-2064 > URL: https://issues.jboss.org/browse/ARQ-2064 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.0.1.Final > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_3.0.0.Alpha1, drone_2.1.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Dec 9 10:57:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 9 Dec 2016 10:57:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2060) Support for Edge browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2060: -------------------------------- Fix Version/s: drone_3.0.0.Alpha1 drone_2.1.0.Alpha1 > Support for Edge browser > ------------------------ > > Key: ARQ-2060 > URL: https://issues.jboss.org/browse/ARQ-2060 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.1.0.Final > Environment: Windows 10 > Reporter: Tomas David > Assignee: Tomas David > Fix For: drone_3.0.0.Alpha1, drone_2.1.0.Alpha1 > > > Edge browser is not currently supported. Available options are: opera, safari, chrome, phantomjs, firefox, htmlUnit, internetExplorer. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Dec 9 10:57:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 9 Dec 2016 10:57:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1695) Integrate Spacelift into Drone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1695: -------------------------------- Fix Version/s: drone_3.0.0.Alpha1 drone_2.1.0.Alpha1 (was: drone_2.1.0.Final) > Integrate Spacelift into Drone > ------------------------------ > > Key: ARQ-1695 > URL: https://issues.jboss.org/browse/ARQ-1695 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Reporter: Karel Piwko > Fix For: drone_3.0.0.Alpha1, drone_2.1.0.Alpha1 > > > Spacelift can be used for following tasks: > * Download and execution of Selenium Server > * Download of ChromeDriver binary > * Download of IEDriver binary (optional, might not be needed as of IE11+) -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Dec 12 06:13:00 2016 From: issues at jboss.org (Vsevolod Golovanov (JIRA)) Date: Mon, 12 Dec 2016 06:13:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-382) Make @InitialPage work for Field In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13337021#comment-13337021 ] Vsevolod Golovanov commented on ARQGRA-382: ------------------------------------------- Meanwhile InitialPage's javadoc's first usage example places it on a field. > Make @InitialPage work for Field > -------------------------------- > > Key: ARQGRA-382 > URL: https://issues.jboss.org/browse/ARQGRA-382 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Affects Versions: 2.0.0.CR1 > Reporter: Karel Piwko > Fix For: 2.0-Tracking > > > While @InitialPage allows to be used on test class field, it does not do anything. > {code} > @InitialPage AddUserPage page; > @Test > void test() { > page.foo() > } > {code} > raises > {code} > java.lang.NullPointerException: null > at com.acme.example.test.DroneTest.addUser(DroneTest.java:35) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Dec 13 08:57:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 13 Dec 2016 08:57:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1695) Integrate Spacelift into Drone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1695: -------------------------------- Fix Version/s: (was: drone_3.0.0.Alpha1) > Integrate Spacelift into Drone > ------------------------------ > > Key: ARQ-1695 > URL: https://issues.jboss.org/browse/ARQ-1695 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Reporter: Karel Piwko > Fix For: drone_2.1.0.Alpha1 > > > Spacelift can be used for following tasks: > * Download and execution of Selenium Server > * Download of ChromeDriver binary > * Download of IEDriver binary (optional, might not be needed as of IE11+) -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Dec 13 08:57:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 13 Dec 2016 08:57:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2060) Support for Edge browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2060: -------------------------------- Fix Version/s: (was: drone_3.0.0.Alpha1) > Support for Edge browser > ------------------------ > > Key: ARQ-2060 > URL: https://issues.jboss.org/browse/ARQ-2060 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.1.0.Final > Environment: Windows 10 > Reporter: Tomas David > Assignee: Tomas David > Fix For: drone_2.1.0.Alpha1 > > > Edge browser is not currently supported. Available options are: opera, safari, chrome, phantomjs, firefox, htmlUnit, internetExplorer. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Dec 13 08:57:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 13 Dec 2016 08:57:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2064) Upgrade JUnit to 4.12 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2064: -------------------------------- Fix Version/s: (was: drone_3.0.0.Alpha1) > Upgrade JUnit to 4.12 > --------------------- > > Key: ARQ-2064 > URL: https://issues.jboss.org/browse/ARQ-2064 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.0.1.Final > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.1.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Dec 13 08:57:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 13 Dec 2016 08:57:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2062) Upgrade jboss-parent to latest version (21) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2062: -------------------------------- Fix Version/s: (was: drone_3.0.0.Alpha1) > Upgrade jboss-parent to latest version (21) > ------------------------------------------- > > Key: ARQ-2062 > URL: https://issues.jboss.org/browse/ARQ-2062 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.0.1.Final > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.1.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Dec 13 08:58:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 13 Dec 2016 08:58:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2063) Upgrade build.gradle file to use Spacelift 17 and Gradle 2.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2063: -------------------------------- Fix Version/s: (was: drone_3.0.0.Alpha1) > Upgrade build.gradle file to use Spacelift 17 and Gradle 2.5 > ------------------------------------------------------------ > > Key: ARQ-2063 > URL: https://issues.jboss.org/browse/ARQ-2063 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.0.1.Final > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.1.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Dec 13 09:15:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 13 Dec 2016 09:15:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2065) Combine multiple test results In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2065: ----------------------------------- Summary: Combine multiple test results Key: ARQ-2065 URL: https://issues.jboss.org/browse/ARQ-2065 Project: Arquillian Issue Type: Feature Request Components: core Affects Versions: 1.1.11.Final Reporter: Bartosz Majsak Priority: Minor With the current implementation in place splitting single test in several executions can only happen from within Arquillian events (so we run n tests from within single test). This in particular happens for running contract tests for Pact, where one test spawns several verifications based on the content of the contract itself. Even though the {{List}} is used as a container object for TestResult instance passed along when Test event is fired, it can happen one test can be fired multiple times (for example in arquillian-algeron). The temporary solution for this problem could be that all the results are collected into one instance of TestResult. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Dec 13 09:16:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 13 Dec 2016 09:16:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2065) Combine multiple test results In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak reassigned ARQ-2065: ----------------------------------- Assignee: Bartosz Majsak > Combine multiple test results > ----------------------------- > > Key: ARQ-2065 > URL: https://issues.jboss.org/browse/ARQ-2065 > Project: Arquillian > Issue Type: Feature Request > Components: core > Affects Versions: 1.1.11.Final > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Minor > > With the current implementation in place splitting single test in several executions can only happen from within Arquillian events (so we run n tests from within single test). This in particular happens for running contract tests for Pact, where one test spawns several verifications based on the content of the contract itself. > Even though the {{List}} is used as a container object for TestResult instance passed along when Test event is fired, it can happen one test can be fired multiple times (for example in arquillian-algeron). > The temporary solution for this problem could be that all the results are collected into one instance of TestResult. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Dec 13 09:16:01 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 13 Dec 2016 09:16:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2065) Combine multiple test results In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2065: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-core/pull/120 > Combine multiple test results > ----------------------------- > > Key: ARQ-2065 > URL: https://issues.jboss.org/browse/ARQ-2065 > Project: Arquillian > Issue Type: Feature Request > Components: core > Affects Versions: 1.1.11.Final > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Minor > > With the current implementation in place splitting single test in several executions can only happen from within Arquillian events (so we run n tests from within single test). This in particular happens for running contract tests for Pact, where one test spawns several verifications based on the content of the contract itself. > Even though the {{List}} is used as a container object for TestResult instance passed along when Test event is fired, it can happen one test can be fired multiple times (for example in arquillian-algeron). > The temporary solution for this problem could be that all the results are collected into one instance of TestResult. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Dec 13 09:17:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 13 Dec 2016 09:17:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2065) Combine multiple test results In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2065: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Combine multiple test results > ----------------------------- > > Key: ARQ-2065 > URL: https://issues.jboss.org/browse/ARQ-2065 > Project: Arquillian > Issue Type: Feature Request > Components: core > Affects Versions: 1.1.11.Final > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Minor > > With the current implementation in place splitting single test in several executions can only happen from within Arquillian events (so we run n tests from within single test). This in particular happens for running contract tests for Pact, where one test spawns several verifications based on the content of the contract itself. > Even though the {{List}} is used as a container object for TestResult instance passed along when Test event is fired, it can happen one test can be fired multiple times (for example in arquillian-algeron). > The temporary solution for this problem could be that all the results are collected into one instance of TestResult. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Dec 15 04:44:00 2016 From: issues at jboss.org (Tobias Stadler (JIRA)) Date: Thu, 15 Dec 2016 04:44:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2066) Supprt for JUnit 5 In-Reply-To: References: Message-ID: Tobias Stadler created ARQ-2066: ----------------------------------- Summary: Supprt for JUnit 5 Key: ARQ-2066 URL: https://issues.jboss.org/browse/ARQ-2066 Project: Arquillian Issue Type: Feature Request Reporter: Tobias Stadler The final relase of JUnit 5 is scheduled for Q1 2017. It would be nice if Arquillian would support it then. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Dec 22 08:25:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 22 Dec 2016 08:25:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1684) Jacoco extension filters do not work as advertised In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1684: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-jacoco/pull/31 > Jacoco extension filters do not work as advertised > -------------------------------------------------- > > Key: ARQ-1684 > URL: https://issues.jboss.org/browse/ARQ-1684 > Project: Arquillian > Issue Type: Bug > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha6 > Reporter: Rich DiCroce > Fix For: jacoco_1.0.0.next > > > The Jacoco includes/excludes mechanism does not work the way the [1.0.0.Alpha5 release announcement|http://arquillian.org/blog/2012/11/27/arquillian-extension-jacoco-1-0-0-Alpha5/] implies it does. Specifically, the release announcement shows excluding a package and then including some sub-packages. This implies that includes have precedence over excludes, but that is not true. It's clear from looking at the source code that includes and excludes just get turned into filters that are all ANDed together. So if you have > exclude some.package.* > include some.package.foo.* > then some.package.foo will not be included because the exclude for some.package will return false. Effectively, excludes have priority over includes. > This would be fine if not for the fact that an "include everything" filter is automatically added. This, combined with exclusions having priority, breaks a key use case, namely: I want to exclude all packages that are not my own code. I can't just > include my.package.* > because of the automatic include all filter, and I can't > exclude * > include my.package.* > because the exclude blocks out the include. > Including everything is a problem because then so many classes have to be instrumented that the test just hangs and the archive never gets deployed. For me, this makes the Jacoco extension completely unusable. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Dec 22 08:25:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 22 Dec 2016 08:25:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1684) Jacoco extension filters do not work as advertised In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak reassigned ARQ-1684: ----------------------------------- Assignee: Bartosz Majsak > Jacoco extension filters do not work as advertised > -------------------------------------------------- > > Key: ARQ-1684 > URL: https://issues.jboss.org/browse/ARQ-1684 > Project: Arquillian > Issue Type: Bug > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha6 > Reporter: Rich DiCroce > Assignee: Bartosz Majsak > Fix For: jacoco_1.0.0.next > > > The Jacoco includes/excludes mechanism does not work the way the [1.0.0.Alpha5 release announcement|http://arquillian.org/blog/2012/11/27/arquillian-extension-jacoco-1-0-0-Alpha5/] implies it does. Specifically, the release announcement shows excluding a package and then including some sub-packages. This implies that includes have precedence over excludes, but that is not true. It's clear from looking at the source code that includes and excludes just get turned into filters that are all ANDed together. So if you have > exclude some.package.* > include some.package.foo.* > then some.package.foo will not be included because the exclude for some.package will return false. Effectively, excludes have priority over includes. > This would be fine if not for the fact that an "include everything" filter is automatically added. This, combined with exclusions having priority, breaks a key use case, namely: I want to exclude all packages that are not my own code. I can't just > include my.package.* > because of the automatic include all filter, and I can't > exclude * > include my.package.* > because the exclude blocks out the include. > Including everything is a problem because then so many classes have to be instrumented that the test just hangs and the archive never gets deployed. For me, this makes the Jacoco extension completely unusable. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Dec 30 05:12:00 2016 From: issues at jboss.org (=?UTF-8?Q?Cristina_Gonz=C3=A1lez_castellano_=28JIRA=29?=) Date: Fri, 30 Dec 2016 05:12:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2067) Can't use the Arquillian Karaf Extension with a remote container In-Reply-To: References: Message-ID: Cristina Gonz?lez castellano created ARQ-2067: ------------------------------------------------- Summary: Can't use the Arquillian Karaf Extension with a remote container Key: ARQ-2067 URL: https://issues.jboss.org/browse/ARQ-2067 Project: Arquillian Issue Type: Bug Components: OSGi Containers Affects Versions: osgi_2.1.0.Final Reporter: Cristina Gonz?lez castellano Assignee: Thomas Diesler I have been trying to use the Arquillian OSGi extension with a Docker container, but I have found the next issue: - When we use JMXDeployableContainer, to deploy a OSGi Bundle to a remote OSGi Karaf, we use a local URL, of the type: file:/var/folders/nq/p1_j3ycj169dzl1ypg8d5zhh0000gn/T/vfs/osgitmp-8888e08d9dca9b47/urlstream-d8ff47698b0d2150/253ae58a-4ad3-4077-b049-281ef1b9d3eb.jar. - Of course this URL doesn't exist in the remote Docker container. - So I get the exception: Caused by: java.io.IOException: Installation of a bundle with location 253ae58a-4ad3-4077-b049-281ef1b9d3eb.jar failed with the message: /var/folders/nq/p1_j3ycj169dzl1ypg8d5zhh0000gn/T/vfs/osgitmp-8888e08d9dca9b47/urlstream-d8ff47698b0d2150/253ae58a-4ad3-4077-b049-281ef1b9d3eb.jar (No such file or directory) Have you faced this issue before? What do you think is the best solution? -- This message was sent by Atlassian JIRA (v7.2.3#72005)