You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by David Karr <da...@gmail.com> on 2022/05/31 13:46:23 UTC
Questions about surefire issue causing "buffer overflow" and apache JIRA problem
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
----------------------------
Re: Questions about surefire issue causing "buffer overflow" and apache JIRA problem
Posted by Slawomir Jaranowski <s....@gmail.com>.
Hi,
Without a project it is difficult to say.
One issue can be that when you have junit-platform-runner on classpath
junit4 provider will be selected. [1]
You can also try to select provider manually [2]
[1] https://issues.apache.org/jira/browse/SUREFIRE-2033
[2]
https://maven.apache.org/surefire/maven-surefire-plugin/examples/providers.html
wt., 31 maj 2022 o 17:17 David Karr <da...@gmail.com> napisał(a):
> I see.
>
> Related to this, I have still another build that is resulting in no JUnit 5
> tests being selected. I have no idea why. Are there any changes going in
> M7 that might address this? I was considering spending the time trying to
> take that test case and whittling it down to something that I can post that
> still demonstrates the problem, although that may take a lot of time and
> not result in something that I can use.
>
> On Tue, May 31, 2022 at 8:03 AM Slawomir Jaranowski <
> s.jaranowski@gmail.com>
> wrote:
>
> > 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 <da...@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
> >
>
--
Sławomir Jaranowski
Re: Questions about surefire issue causing "buffer overflow" and apache JIRA problem
Posted by David Karr <da...@gmail.com>.
I see.
Related to this, I have still another build that is resulting in no JUnit 5
tests being selected. I have no idea why. Are there any changes going in
M7 that might address this? I was considering spending the time trying to
take that test case and whittling it down to something that I can post that
still demonstrates the problem, although that may take a lot of time and
not result in something that I can use.
On Tue, May 31, 2022 at 8:03 AM Slawomir Jaranowski <s....@gmail.com>
wrote:
> 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 <da...@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
>
Re: Questions about surefire issue causing "buffer overflow" and apache JIRA problem
Posted by Slawomir Jaranowski <s....@gmail.com>.
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 <da...@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