You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Robert Middleton <os...@gmail.com> on 2020/09/06 18:54:23 UTC
[log4cxx] Tests and auto-builds
Thorsten, do all of the tests pass for you? The reason I ask is because
the 'encodingtest' always fails for me. I've gotten the build to run with
Github Actions as well, and it always fails there as well, so maybe there's
some sort of locale/encoding issue going on?
One of the tests currently fails on OSX as well with a segfault, which is
the same thing that Ralph indicated a few weeks ago. I have an old mac
that I can try to reproduce it on, but if anybody has a chance sometime to
help debug this I would appreciate it.
-Robert Middleton
Re: [log4cxx] Tests and auto-builds
Posted by Robert Middleton <os...@gmail.com>.
Figured it out. Apparently when I checked out the code, I indicated that
git should convert the \n to \r\n(native line ending on Windows), which
causes the tests to fail, as the "known-good" files were subtly changed
with their line endings, which caused the (binary) comparison to fail.
Fortunately, adding a .gitattributes file fixes this issue. I'll put that
up shortly, and then do a bigger PR with the github actions sometime soon,
hopefully with the OSX crash fixed.
-Robert Middleton
On Mon, Sep 7, 2020 at 3:23 AM Thorsten Schöning <ts...@am-soft.de>
wrote:
> Guten Tag Robert Middleton,
> am Sonntag, 6. September 2020 um 20:54 schrieben Sie:
>
> > Thorsten, do all of the tests pass for you? The reason I ask is because
> > the 'encodingtest' always fails for me. I've gotten the build to run
> with
> > Github Actions as well, and it always fails there as well, so maybe
> there's
> > some sort of locale/encoding issue going on?
>
> It works for me when running in Visual Studio with pretty much default
> installation, executing "ctest" manually on the old "cmd.exe" and
> doing the same with Powershell as well. I just pulled your merged PR
> and tested with MASTER after removing all old CMAKE- and VS-related
> directories from the project.
>
> I did NOT customize any string-related options of the CMAKE-build, so
> whatever the build defaults to should be used in my environment.
>
> Additionally, running the tests after building with Embarcadero RAD
> Studio 10.2 on "cmd.exe" succeeds as well. One important difference is
> that I'm using the wchar_t-API of log4cxx in those cases.
>
> Running those tests additionall results in lots of output on the
> console, which is not the case for "ctest". There's e.g. the following
> first line, but nothing more specifically focussing "encodingtest":
>
> > LC_CTYPE: LC_CTYPE=German_Germany.850
> > [...]
> > encodingtest : SUCCESS
>
> Do you get any useful error output at all somewhere? If not, not using
> "ctest" in favour of a plain exe might help debugging. I've uploaded
> my built projects somewhere, just if it is of any help:
>
> https://gofile.io/d/xvkWcK
>
> The attached mail contains infos about where to place things.
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
> --
> Thorsten Schöning E-Mail: Thorsten.Schoening@AM-SoFT.de
> AM-SoFT IT-Systeme http://www.AM-SoFT.de/
>
> Telefon...........05151- 9468- 55
> Fax...............05151- 9468- 88
> Mobil..............0178-8 9468- 04
>
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: [log4cxx] Tests and auto-builds
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag Robert Middleton,
am Sonntag, 6. September 2020 um 20:54 schrieben Sie:
> Thorsten, do all of the tests pass for you? The reason I ask is because
> the 'encodingtest' always fails for me. I've gotten the build to run with
> Github Actions as well, and it always fails there as well, so maybe there's
> some sort of locale/encoding issue going on?
It works for me when running in Visual Studio with pretty much default
installation, executing "ctest" manually on the old "cmd.exe" and
doing the same with Powershell as well. I just pulled your merged PR
and tested with MASTER after removing all old CMAKE- and VS-related
directories from the project.
I did NOT customize any string-related options of the CMAKE-build, so
whatever the build defaults to should be used in my environment.
Additionally, running the tests after building with Embarcadero RAD
Studio 10.2 on "cmd.exe" succeeds as well. One important difference is
that I'm using the wchar_t-API of log4cxx in those cases.
Running those tests additionall results in lots of output on the
console, which is not the case for "ctest". There's e.g. the following
first line, but nothing more specifically focussing "encodingtest":
> LC_CTYPE: LC_CTYPE=German_Germany.850
> [...]
> encodingtest : SUCCESS
Do you get any useful error output at all somewhere? If not, not using
"ctest" in favour of a plain exe might help debugging. I've uploaded
my built projects somewhere, just if it is of any help:
https://gofile.io/d/xvkWcK
The attached mail contains infos about where to place things.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail: Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow