Oops, “reified” should say “memoized”. You get the idea.
—
Matt Sicker
> On Nov 17, 2022, at 22:12, mattsic...@apache.org wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> mattsicker pushed a commit to branch master
> in repository
I made that change to log4j-api-test and that fixed the problem.
Ralph
> On Nov 17, 2022, at 3:29 PM, Piotr P. Karwasz wrote:
>
> On Thu, 17 Nov 2022 at 23:23, Ralph Goers wrote:
>>
>> I ran mvn test -Dtest=LoggerTest and it still fails.
>
> In `release-2.x` JUnit 5 is configured with:
>
>
On Thu, 17 Nov 2022 at 23:23, Ralph Goers wrote:
>
> I ran mvn test -Dtest=LoggerTest and it still fails.
In `release-2.x` JUnit 5 is configured with:
junit.jupiter.execution.parallel.mode.default = concurrent
In `master` we have:
junit.jupiter.execution.parallel.mode.default = same_thread
I ran mvn test -Dtest=LoggerTest and it still fails.
Ralph
> On Nov 17, 2022, at 12:27 PM, Matt Sicker wrote:
>
> There’s a random seed value output for each run as the test order is
> randomized. You can use the seed to replay a particular test ordering, though
> if it’s a bug, it’ll still
There’s a random seed value output for each run as the test order is
randomized. You can use the seed to replay a particular test ordering, though
if it’s a bug, it’ll still likely only show up randomly.
> On Nov 17, 2022, at 5:23 AM, Gary Gregory wrote:
>
> The stack bottom shows
>
>
I haven’t tried master recently. The failures I am seeing are in release-2.x.
Ralph
> On Nov 17, 2022, at 10:23 AM, Piotr P. Karwasz
> wrote:
>
> Hi Gary,
>
> On Thu, 17 Nov 2022 at 12:24, Gary Gregory wrote:
>> I hope we are not running tests in parallel or else how can we be reliable
>>
Hi Gary,
On Thu, 17 Nov 2022 at 12:24, Gary Gregory wrote:
> I hope we are not running tests in parallel or else how can we be reliable
> and reproducible? And compare builds between developers?
Yes, `log4j-api-test` is configured to run in parallel (at least in
`master`). This setting has been
On Windows, I get:
[INFO] Running org.apache.logging.log4j.status.StatusConsoleListenerTest
[ERROR] Tests run: 41, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.042
s <<< FAILURE! - in org.apache.logging.log4j.spi.MutableThreadContextStackTest
[ERROR]
Consistent
Ralph
> On Nov 16, 2022, at 5:23 PM, Matt Sicker wrote:
>
> Is this a consistent failure or random?
>
>> On Nov 16, 2022, at 3:42 PM, Ralph Goers wrote:
>>
>> I haven’t run a build in a while and looking at the recent commits I am not
>> sure what is causing this, but some
The stack bottom shows
java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157)
I hope we are not running tests in parallel or else how can we be reliable
and reproducible? And compare builds between developers?
Gary
On Wed, Nov 16, 2022, 19:23 Matt Sicker wrote:
> Is
10 matches
Mail list logo
