Hi Ralph,
On Mon, 30 May 2022 at 00:26, Ralph Goers
wrote:
> FWIW, the h2 upgrade broke the build. I am in the process of reverting the
> version change.
>
> Ralph
>
I would really like the H2 upgrade to be included in 2.18.0, so that pages
like this:
https://mvnrepository.com/artifact/org.apa
Hi Ralph,
On Mon, 30 May 2022 at 00:14, Ralph Goers
wrote:
> Running the test individually shows
>
> Caused by: org.h2.mvstore.MVStoreException: The write format 1 is smaller
> than the supported format 2 [2.1.212/5]
>
> So the h2 dependency upgrade apparently wasn’t tested.
>
You need to clean
FWIW, the h2 upgrade broke the build. I am in the process of reverting the
version change.
Ralph
> On May 25, 2022, at 10:30 PM, Piotr P. Karwasz
> wrote:
>
> Hi Ralph,
>
> On Thu, 26 May 2022 at 06:47, Ralph Goers
> wrote:
>
>> If you are confident in it then feel free to commit it. Remem
Running the test individually shows
Caused by: org.h2.mvstore.MVStoreException: The write format 1 is smaller than
the supported format 2 [2.1.212/5]
So the h2 dependency upgrade apparently wasn’t tested.
Ralph
> On May 29, 2022, at 3:09 PM, Ralph Goers wrote:
>
> Out of the blue my release-
Out of the blue my release-2.x build is failing on my Mac with
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR] JdbcAppenderColumnMappingLiteralTest.test » JdbcSQLNonTransient
General error: "The write format 1 is smaller than the supported format 2
[2.1.212/5]" [5-212]
This class hasn’t
This is much nicer, thanks!
—
Matt Sicker
> On May 29, 2022, at 03:05, rgo...@apache.org wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> rgoers pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
>
> commit
I ported more tests to JUnit 5. Assuming those are the same, then it’s a
Windows-specific issue in the CleanUpDirectories/Files annotations compared to
the JUnit 4 test rules for doing the same. Since the extension mechanisms in
JUnit are different, there could potentially be a bug due to orderi
They referred to the tests. Do you know a commit they worked at?
Tim
> On May 29, 2022, at 12:43 PM, Ralph Goers wrote:
>
> Who is they? You mean me? This is on the master branch. It has never been
> released.
>
> Ralph
>
>> On May 29, 2022, at 12:31 PM, Tim Perry wrote:
>>
>> Do you re
Who is they? You mean me? This is on the master branch. It has never been
released.
Ralph
> On May 29, 2022, at 12:31 PM, Tim Perry wrote:
>
> Do you remember the last release they worked in. I could use git bisect to
> find when they broke if I have a good starting point. I have some time t
Do you remember the last release they worked in. I could use git bisect to find
when they broke if I have a good starting point. I have some time to run it
this afternoon…,
Tim
Tim Perry
(916) 505-3634
> On May 29, 2022, at 11:44 AM, Ralph Goers wrote:
>
> So I have been trying to fix the
So I have been trying to fix the problems on Windows in the unit test I added
recently. I think I have finally fixed that but I just updated from master and
now I am getting all the errors below. Did something change?
Ralph
[ERROR] Failures:
[ERROR] RollingAppenderCronEvery2DirectTest.testApp
Matt,
So you disabled this test. However, you didn’t notice that you modified this
test and broke it. If you compare your changes to the previous version you will
see that you changed the name of the Logger in the code so that it no longer
matches the configuration.
Perhaps rather than disabli
That is OK. I have reverted your commit and am testing the build for a second
time doing it the correct way.
Ralph
> On May 28, 2022, at 9:14 PM, Matt Sicker wrote:
>
> It worked, but I had to specify where the parent pom was in the submodules.
> Are you saying I could get the same effect by
13 matches
Mail list logo
