[jira] [Updated] (LOGCXX-562) New github actions for automation
[
https://issues.apache.org/jira/browse/LOGCXX-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Middleton updated LOGCXX-562:
Fix Version/s: 0.13.1
> New github actions for automation
> -
>
> Key: LOGCXX-562
> URL: https://issues.apache.org/jira/browse/LOGCXX-562
> Project: Log4cxx
> Issue Type: New Feature
>Reporter: Robert Middleton
>Priority: Major
> Fix For: 0.13.1
>
>
> The following features/configurations should have github actions associated
> with them to ensure that things will build:
> * Windows Static build
> ** Tests should run with this build as well
> * version of \{fmt}
> ** We may want to test multiple versions of \{fmt}
> ** Relates to LOGCXX-514
> * Build in C++11 mode(use Boost for newer features)
> * Disable network support
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (LOGCXX-562) New github actions for automation
[
https://issues.apache.org/jira/browse/LOGCXX-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Middleton resolved LOGCXX-562.
-
Resolution: Fixed
> New github actions for automation
> -
>
> Key: LOGCXX-562
> URL: https://issues.apache.org/jira/browse/LOGCXX-562
> Project: Log4cxx
> Issue Type: New Feature
>Reporter: Robert Middleton
>Priority: Major
> Fix For: 0.13.1
>
>
> The following features/configurations should have github actions associated
> with them to ensure that things will build:
> * Windows Static build
> ** Tests should run with this build as well
> * version of \{fmt}
> ** We may want to test multiple versions of \{fmt}
> ** Relates to LOGCXX-514
> * Build in C++11 mode(use Boost for newer features)
> * Disable network support
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (LOGCXX-491) SizeBasedRollingTest cases fail when defining LOG4CXX_MULTI_PROCESS
[
https://issues.apache.org/jira/browse/LOGCXX-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Middleton resolved LOGCXX-491.
-
Resolution: Fixed
With the merge of LOGCXX-518, all of the multiprocess stuff has been broken out
into separate classes so that the specific case of multiprocess logging doesn't
affect the default rolling file behavior.
> SizeBasedRollingTest cases fail when defining LOG4CXX_MULTI_PROCESS
> ---
>
> Key: LOGCXX-491
> URL: https://issues.apache.org/jira/browse/LOGCXX-491
> Project: Log4cxx
> Issue Type: Bug
> Components: Tests
>Affects Versions: 0.11.0
> Environment: gcc version 4.4.7 20120313 (Red Hat 4.4.7-17) (GCC)
> gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
>Reporter: Sean P. Miller
>Priority: Minor
> Fix For: 1.0.0
>
>
> I've encountered this with revisions 1755031 and 1802636 on both environments
> listed. Abbreviated debugging session:
> {noformat}
> ubuntu@ip-[...]:~/dev/log4cxx$ gdb src/test/cpp/.libs/lt-testsuite
> [...]
> Reading symbols from src/test/cpp/.libs/lt-testsuite...done.
> (gdb) run -v sizebasedrollingtest
> Starting program: /home/ubuntu/dev/log4cxx/src/test/cpp/.libs/lt-testsuite -v
> sizebasedrollingtest
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> LC_CTYPE: en_US.UTF-8
> sizebasedrollingtest: -2017-07-21 19:28:52,889 DEBUG
> org.apache.log4j.rolling.SizeBasedRollingTest -Hello---0
> 2017-07-21 19:28:52,889 DEBUG org.apache.log4j.rolling.SizeBasedRollingTest
> -Hello---1
> [...]
> 2017-07-21 19:28:52,898 DEBUG org.apache.log4j.rolling.SizeBasedRollingTest
> -Hello---9
> 2017-07-21 19:28:52,898 DEBUG org.apache.log4j.rolling.SizeBasedRollingTest
> -Hello--10
> log4cxx: Exception during rollover
> Program received signal SIGSEGV, Segmentation fault.
> log4cxx::rolling::RollingFileAppenderSkeleton::subAppend (this=0x757d40,
> event=..., p=...) at rollingfileappender.cpp:378
> 378 apr_file_t* _fd =
> getWriter()->getOutPutStreamPtr()->getFileOutPutStreamPtr().getFilePtr();
> (gdb) bt
> #0 log4cxx::rolling::RollingFileAppenderSkeleton::subAppend (this=0x757d40,
> event=..., p=...) at rollingfileappender.cpp:378
> #1 0x7766adc2 in log4cxx::AppenderSkeleton::doAppend (this=0x757d40,
> event=..., pool1=...) at appenderskeleton.cpp:142
> #2 0x77668abf in
> log4cxx::helpers::AppenderAttachableImpl::appendLoopOnAppenders
> (this=0x7574e0, event=..., p=...) at appenderattachableimpl.cpp:69
> #3 0x776b07e8 in log4cxx::Logger::callAppenders
> (this=this@entry=0x757400, event=..., p=...) at logger.cpp:96
> #4 0x776b0a3e in log4cxx::Logger::forcedLog (this=0x757400,
> level1=..., message="Hello--10", location=...) at logger.cpp:127
> #5 0x004845e3 in SizeBasedRollingTest::common (logger1=...,
> this=0x7fffe150) at rolling/sizebasedrollingtest.cpp:88
> #6 SizeBasedRollingTest::test6 (this=0x7fffe150) at
> rolling/sizebasedrollingtest.cpp:339
> #7 0x00489366 in LogUnit::runTest
> (tc=0x7fffe3a0, func=(void (SizeBasedRollingTest::*)(SizeBasedRollingTest
> * const)) 0x483e30 ) at
> rolling/../logunit.h:112
> #8 0x004898c0 in
> SizeBasedRollingTest::RegisterSuite::test6Registration::run (tc= out>) at rolling/sizebasedrollingtest.cpp:57
> #9 0x004b4005 in abts_run_test (ts=ts@entry=0x74ee20, f=0x4898b0
> void*)>, value=value@entry=0x0) at abts.cpp:174
> #10 0x004c7cf1 in LogUnit::TestSuite::run (this=0x734f20
> , suite=suite@entry=0x74ee20) at
> logunit.cpp:232
> #11 0x004c7f28 in abts_run_suites (suite=0x74ee20, suite@entry=0x0)
> at logunit.cpp:59
> #12 0x0041bd7d in main (argc=3, argv=0x7fffe558) at abts.cpp:433
> (gdb)
> {noformat}
> Diff applied for multi-process support:
> {noformat}
> diff -urN log4cxx-0.11.0.orig/configure.ac log4cxx-0.11.0/configure.ac
> --- log4cxx-0.11.0.orig/configure.ac 2016-08-26 16:32:29.20500 +
> +++ log4cxx-0.11.0/configure.ac 2016-08-26 16:32:55.91900 +
> @@ -55,6 +55,8 @@
> AC_PROG_CXXCPP
> AC_LANG(C++)
>
> +AC_DEFINE(LOG4CXX_MULTI_PROCESS)
> +
> # CXX fine tuning
> case "$host" in
> *-dec-osf*)
> {noformat}
> Tests run via {{make check}}. I believe this is v0.11.0 code (?).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (LOGCXX-518) Refactor the multi process code of RollingFileAppender
[ https://issues.apache.org/jira/browse/LOGCXX-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Middleton resolved LOGCXX-518. - Resolution: Fixed > Refactor the multi process code of RollingFileAppender > -- > > Key: LOGCXX-518 > URL: https://issues.apache.org/jira/browse/LOGCXX-518 > Project: Log4cxx > Issue Type: New Feature >Reporter: Robert Middleton >Assignee: Robert Middleton >Priority: Major > Fix For: 1.0.0 > > > The LOG4CXX_MULTI_PROCESS macro works only with the RollingFileAppender in > order to have multiple processes log to the same file and rollover correctly. > > Currently, this is only able to be set at compile time, somewhat limiting its > usefulness. Either refactor into a separate class, or create a new option to > activate this feature. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [logging-log4cxx] rm5248 merged pull request #143: LOGCXX-518 Refactor of RollingFileAppender for multiprocess
rm5248 merged PR #143: URL: https://github.com/apache/logging-log4cxx/pull/143 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [logging-log4cxx] rm5248 merged pull request #144: LOGCXX-562
rm5248 merged PR #144: URL: https://github.com/apache/logging-log4cxx/pull/144 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [logging-log4cxx] rm5248 opened a new pull request, #144: LOGCXX-562
rm5248 opened a new pull request, #144: URL: https://github.com/apache/logging-log4cxx/pull/144 Reorganize workflows to handle more combinations of options. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (LOG4J2-3019) HtmlLayoutTest.testLayoutWithDatePatternFixedFormat test fails on windows
[
https://issues.apache.org/jira/browse/LOG4J2-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17625764#comment-17625764
]
Volkan Yazici commented on LOG4J2-3019:
---
Thanks for the PR [~adwsingh], LGTM, merged.
> HtmlLayoutTest.testLayoutWithDatePatternFixedFormat test fails on windows
> -
>
> Key: LOG4J2-3019
> URL: https://issues.apache.org/jira/browse/LOG4J2-3019
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.14.0
> Environment: OS: Windows 10 Enterprise
> Version: 20H2
> OS Build: 19042.746
> Experience: Windows Feature Experience Pack 120.2212.551.0
> java version "1.8.0_192"
> Java(TM) SE Runtime Environment (build 1.8.0_192-b12)
> Java HotSpot(TM) 64-Bit Server VM (build 25.192-b12, mixed mode)
>Reporter: Luc Kleeven
>Assignee: Volkan Yazici
>Priority: Minor
> Fix For: 2.18.0
>
>
> When running a './mvnw verify' on the 'release-2.x' branche, last commit id
> '9788f33fc62b3b4012489a603772433d3440e6b0'. The following test fails:
> {code:java}
> [ERROR]
> HtmlLayoutTest.testLayoutWithDatePatternFixedFormat:242->testLayoutWithDatePatternFixedFormat:273
> Incorrect date=02 Nov 2012 21:34:02,123, format=DATE,
> timezone=GMT+8 ==> expected: <02 nov 2012 21:34:02,123> but was:
> <02 Nov 2012 21:34:02,123> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [logging-log4j2] vy merged pull request #1127: [LOG4J2-3019] Fixing HtmlLayoutTest when timezone has minutes
vy merged PR #1127: URL: https://github.com/apache/logging-log4j2/pull/1127 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
