Hi,

M7 should be released soon, please follow the discussion on dev list [1]

[1] https://lists.apache.org/thread/r86q92w8pfb1g3rg8tzbt810cjt6vdcq

wt., 31 maj 2022 o 15:47 David Karr <davidmichaelk...@gmail.com> napisał(a):

> I noticed the following issue:
> https://issues.apache.org/jira/browse/SUREFIRE-2056
>
> I searched for it because we are seeing this in one of our builds.
>
> I could use some more information about this.  This is apparently a bug in
> 3.0.0-M6, which is fixed in 3.0.0-M7, which is not released yet. I verified
> that backing off to 3.0.0-M5 avoids this problem, but we are already forced
> to use 3.0.0-M6 because test suites don't work in the last release.
>
> Is there some other workaround we might be able to implement besides
> backing off to 3.0.0-M5?  The problem seems to occur when this "testRunId"
> is null, but I don't know what this is, or how it might be controlled or
> configured in user code.
>
> Note that I tried to write this comment in the issue after logging in, but
> each time I have attempted this (several times over the last few days), it
> says:
> -------------------------
> Communications Breakdown
>
> The Jira server could not be contacted. This may be a temporary glitch or
> the server may be down.
>
> Close this dialog and press refresh in your browser
> ----------------------------
>


-- 
Sławomir Jaranowski

Reply via email to