I've migrated the Arquillian Spock Extension to use a
SessionLauncherListener (see the latest commits at
https://github.com/topicusonderwijs/arquillian-testrunner-spock/tree/spock-2.0-junit5
). This now works perfectly with the updated maven-surefire-plugin.
Arquillian is now only started once per
+1
On Mon, Sep 13, 2021 at 10:49 AM Michael Osipov wrote:
> Hi,
>
> We solved 14 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828&version=12350600
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3
Am 2021-09-13 um 10:49 schrieb Michael Osipov:
Hi,
We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828&version=12350600
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20SCM%20AND%20resolutio
Hi,
We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828&version=12350600
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20SCM%20AND%20resolution%20%3D%20Unresolved
Staging repo:
https://reposit
Hi Marc,
With forkCount = 1 it works fine, the problem is with forkCount > 1. The
Arquillian extension registers its state in the store at the root of the
TestPlan. When running with forkCount > 1, surefire sets up a load balancer
in the main process. This load balancer streams tests one by one to
