Re: Build failed in Jenkins: logging-log4net » feature/RollingFileAppender-NG #4

Looks like this is working too. Changes to the branch develop also causes merge requests against that branch to be merged and built. Thats great stuff to have, but also means that pull requests that stay open for long are going to fill our inboxes. What do you think? Should pull request builds fail

[jira] [Commented] (LOG4J2-928) Lock-free synchronous sub-microsecond appender

[ https://issues.apache.org/jira/browse/LOG4J2-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071518#comment-16071518 ] ASF GitHub Bot commented on LOG4J2-928: --- Github user jvz commented on the issue:

[GitHub] logging-log4j2 issue #87: [LOG4J2-928] Mostly wait-free MemoryMappedFileMana...

Github user jvz commented on the issue: https://github.com/apache/logging-log4j2/pull/87 I'll try to run those benchmarks on an AWS instance next week, though that's not an ideal place to benchmark due to noisy neighbours and that sort of thing. --- If your project is set up for it,

[jira] [Commented] (LOG4J2-928) Lock-free synchronous sub-microsecond appender

[ https://issues.apache.org/jira/browse/LOG4J2-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071511#comment-16071511 ] ASF GitHub Bot commented on LOG4J2-928: --- Github user leventov commented on the issue

[GitHub] logging-log4j2 issue #87: [LOG4J2-928] Mostly wait-free MemoryMappedFileMana...

Github user leventov commented on the issue: https://github.com/apache/logging-log4j2/pull/87 Throughput comparison First number is the number of threads, "150" is the message size. Before this PR ``` 1 - o.a.l.l.p.j.Log4j2AppenderComparisonBenchmark.end2endMMap

[jira] [Commented] (LOG4J2-928) Lock-free synchronous sub-microsecond appender

[ https://issues.apache.org/jira/browse/LOG4J2-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071507#comment-16071507 ] ASF GitHub Bot commented on LOG4J2-928: --- Github user leventov commented on the issue

[GitHub] logging-log4j2 issue #87: [LOG4J2-928] Mostly wait-free MemoryMappedFileMana...

Github user leventov commented on the issue: https://github.com/apache/logging-log4j2/pull/87 Latency comparison ``` java -jar log4j-perf/target/benchmarks.jar ".*Log4j2AppenderLatencyBenchmark.end2end" -f 1 -wi 1 -i 30 -t 2 -p loggerType=MMap ``` On my MBP with 4

[jira] [Comment Edited] (LOG4J2-928) Lock-free synchronous sub-microsecond appender

[ https://issues.apache.org/jira/browse/LOG4J2-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071465#comment-16071465 ] Remko Popma edited comment on LOG4J2-928 at 7/2/17 1:23 AM: I

[jira] [Commented] (LOG4J2-928) Lock-free synchronous sub-microsecond appender

[ https://issues.apache.org/jira/browse/LOG4J2-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071465#comment-16071465 ] Remko Popma commented on LOG4J2-928: I care less for single-threaded throughput. I wou

[jira] [Comment Edited] (LOG4J2-928) Lock-free synchronous sub-microsecond appender

[ https://issues.apache.org/jira/browse/LOG4J2-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071465#comment-16071465 ] Remko Popma edited comment on LOG4J2-928 at 7/2/17 1:09 AM: I

[jira] [Comment Edited] (LOG4J2-928) Lock-free synchronous sub-microsecond appender

[ https://issues.apache.org/jira/browse/LOG4J2-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071465#comment-16071465 ] Remko Popma edited comment on LOG4J2-928 at 7/2/17 1:09 AM: I

Build failed in Jenkins: logging-log4net » feature/RollingFileAppender-NG #4

See -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Obtained Jenkinsfile from 2bd214a79bc0cf9654875b

Build failed in Jenkins: logging-log4net » PR-1 #4

See -- [...truncated 566 B...] Fetching upstream changes from https://github.com/apache/logging-log4net.git > git --version # timeout=10 using GIT_ASKPASS to set credentials dpsenne

Build failed in Jenkins: logging-log4net » PR-2 #4

See -- [...truncated 1.76 KB...] > git rev-list 28f46610fc8b42f7bd4d93a85916164210a5bd24 # timeout=10 [Pipeline] node Still waiting to schedule task Waiting for next available execu

Build failed in Jenkins: logging-log4net » PR-4 #4

See -- [...truncated 19.28 KB...] check-sdkdoc-debug: check-current-build-config: check-build-debug: check-build-defines: set-net-4.5-runtime-configuration: check-log4net-

[jira] [Commented] (LOG4J2-928) Lock-free synchronous sub-microsecond appender

[ https://issues.apache.org/jira/browse/LOG4J2-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071426#comment-16071426 ] Gary Gregory commented on LOG4J2-928: - If are going to potentially loose throughput,

Build failed in Jenkins: log4net-trunk-build #210

See Changes: [dpsenner] Refactored jenkinsfile [dpsenner] Added a few more usecases to the jenkinsfile [dpsenner] Fixed jenkinsfile syntax error [dpsenner] Fixed typo [dpsenner] Added agent any at pipelines

[jira] [Commented] (LOG4J2-928) Lock-free synchronous sub-microsecond appender

[ https://issues.apache.org/jira/browse/LOG4J2-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071395#comment-16071395 ] ASF GitHub Bot commented on LOG4J2-928: --- Github user leventov commented on a diff in

[jira] [Commented] (LOG4J2-928) Lock-free synchronous sub-microsecond appender

[ https://issues.apache.org/jira/browse/LOG4J2-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071394#comment-16071394 ] ASF GitHub Bot commented on LOG4J2-928: --- Github user leventov commented on the issue

[GitHub] logging-log4j2 pull request #87: [LOG4J2-928] Mostly wait-free MemoryMappedF...

Github user leventov commented on a diff in the pull request: https://github.com/apache/logging-log4j2/pull/87#discussion_r125168798 --- Diff: log4j-core/src/main/java/org/apache/logging/log4j/core/appender/ThreadHints.java --- @@ -0,0 +1,63 @@ +/* + * Licensed to the Apac

[GitHub] logging-log4j2 issue #87: [LOG4J2-928] Mostly wait-free MemoryMappedFileMana...

Github user leventov commented on the issue: https://github.com/apache/logging-log4j2/pull/87 @remkop note that this PR is primarily about _latency_, not throughput at all. I will do some testing, but if the throughput will degrade (that I expect in a single-thread case), and latency

[jira] [Commented] (LOG4J2-928) Lock-free synchronous sub-microsecond appender

[ https://issues.apache.org/jira/browse/LOG4J2-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071393#comment-16071393 ] ASF GitHub Bot commented on LOG4J2-928: --- Github user leventov commented on the issue

[GitHub] logging-log4j2 issue #87: [LOG4J2-928] Mostly wait-free MemoryMappedFileMana...

Github user leventov commented on the issue: https://github.com/apache/logging-log4j2/pull/87 @remkop > MemoryMappedFileManager::switchRegion and ::closeAndSwitchRegionWhileLocked should not throw Error: generally a logging problem should not bring down the application. See

[jira] [Updated] (LOG4PHP-238) Logging from (ppid) class destructor fails after forked child processes exit gracefully

[ https://issues.apache.org/jira/browse/LOG4PHP-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ludvik Jerabek updated LOG4PHP-238: --- Description: The issue appear to only manifest itself when implementing class level logging.

[jira] [Updated] (LOG4PHP-238) Logging from (ppid) class destructor fails after forked child processes exit gracefully

[ https://issues.apache.org/jira/browse/LOG4PHP-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ludvik Jerabek updated LOG4PHP-238: --- Summary: Logging from (ppid) class destructor fails after forked child processes exit gracefu

[jira] [Updated] (LOG4PHP-238) Logging from class destructor fails when after forked child processes exit gracefully

[ https://issues.apache.org/jira/browse/LOG4PHP-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ludvik Jerabek updated LOG4PHP-238: --- Summary: Logging from class destructor fails when after forked child processes exit gracefull

[jira] [Created] (LOG4PHP-238) Logging from class destructor fails when from forked child processes

Ludvik Jerabek created LOG4PHP-238: -- Summary: Logging from class destructor fails when from forked child processes Key: LOG4PHP-238 URL: https://issues.apache.org/jira/browse/LOG4PHP-238 Project: Log

Re: [log4net] set up basic multibranch and pull requests build

An idea crossed my mind. Couldn't we build the Mono binaries on the ubuntu machines? .net core should build both on ubuntu and on windows. nant is available also for ubuntu and a perfect candidate for a build tool. It would be even nicer if we could simply add mono as a dependency (i.e. nuget) and

Re: [log4net] set up basic multibranch and pull requests build

Hi Here comes a little heads up on this topic. I was able to get the Jenkinsfile so far that it builds the codebase, tests it on .net 4.0 and builds the site along with the rat report. We are half way to building a release with jenkins. The pipeline looks like this: https://builds.apache.org/job/

Jenkins build became unstable: Log4j 2.x #2859

See

Re: [log4net] pull request #11

Sounds like a plan that is fine with me given that this is just a minor change. 2017-07-01 18:22 GMT+02:00 Stefan Bodewig : > On 2017-06-30, Dominik Psenner wrote: > > > While working on the Jenkinsfile so that jjenkins builds all kinds of > > branches for us I noticed that pr-11 made it into mas

Re: [log4net] pull request #11

On 2017-06-30, Dominik Psenner wrote: > While working on the Jenkinsfile so that jjenkins builds all kinds of > branches for us I noticed that pr-11 made it into master without us carving > out a release. It's been my fault. I committed it to master out of habit and merged it to develop later whe

[jira] [Commented] (LOG4J2-928) Lock-free synchronous sub-microsecond appender

[ https://issues.apache.org/jira/browse/LOG4J2-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071308#comment-16071308 ] ASF GitHub Bot commented on LOG4J2-928: --- Github user remkop commented on the issue:

[GitHub] logging-log4j2 issue #87: [LOG4J2-928] Mostly wait-free MemoryMappedFileMana...

Github user remkop commented on the issue: https://github.com/apache/logging-log4j2/pull/87 Roman, one more thing: since this is a non-trivial patch, would you mind submitting an [ICLA](http://www.apache.org/licenses/#clas)? --- If your project is set up for it, you can reply to thi

[jira] [Commented] (LOG4J2-928) Lock-free synchronous sub-microsecond appender

[ https://issues.apache.org/jira/browse/LOG4J2-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071300#comment-16071300 ] ASF GitHub Bot commented on LOG4J2-928: --- Github user remkop commented on the issue:

[GitHub] logging-log4j2 issue #87: [LOG4J2-928] Mostly wait-free MemoryMappedFileMana...

Github user remkop commented on the issue: https://github.com/apache/logging-log4j2/pull/87 Roman, I started to review your patch. Initial feedback below (still reading): * MemoryMappedFileManager::switchRegion should not throw Error: generally a logging problem should not br

[jira] [Commented] (LOG4J2-1908) Cryptic error message when misconfigured with File and RollingRandomAccessFile appenders targeting same file

[ https://issues.apache.org/jira/browse/LOG4J2-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071264#comment-16071264 ] ASF subversion and git services commented on LOG4J2-1908: - Commit

[jira] [Resolved] (LOG4J2-1261) Replace usage of deprecated LMAX Disruptor APIs

[ https://issues.apache.org/jira/browse/LOG4J2-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1261. - Resolution: Fixed Fix Version/s: 2.9 Fixed in master. Sorry for the wait, Gary! > Replac

[jira] [Commented] (LOG4J2-1261) Replace usage of deprecated LMAX Disruptor APIs

[ https://issues.apache.org/jira/browse/LOG4J2-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071243#comment-16071243 ] ASF subversion and git services commented on LOG4J2-1261: - Commit

[jira] [Updated] (LOG4J2-1261) Replace usage of deprecated LMAX Disruptor APIs

[ https://issues.apache.org/jira/browse/LOG4J2-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1261: External issue ID: https://github.com/LMAX-Exchange/disruptor/issues/148 > Replace usage of depreca

[jira] [Closed] (LOG4J2-1285) AsyncLogger should not use deprecated Disruptor constructors

[ https://issues.apache.org/jira/browse/LOG4J2-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1285. --- Resolution: Duplicate Fix Version/s: 2.9 > AsyncLogger should not use deprecated Disruptor con

[jira] [Closed] (LOG4J2-1801) Add more detail to WARN Ignoring log event after log4j was shut down

[ https://issues.apache.org/jira/browse/LOG4J2-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1801. --- Resolution: Fixed > Add more detail to WARN Ignoring log event after log4j was shut down > --

[jira] [Reopened] (LOG4J2-1801) Add more detail to WARN Ignoring log event after log4j was shut down

[ https://issues.apache.org/jira/browse/LOG4J2-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-1801: - > Add more detail to WARN Ignoring log event after log4j was shut down >

[jira] [Updated] (LOG4J2-1963) Usage of braces in filePattern creates unexpected behaviors

[ https://issues.apache.org/jira/browse/LOG4J2-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Sazzadul Hoque updated LOG4J2-1963: - Description: Consider my following code: {quote}{code:java} import org.apache.logging.lo

[jira] [Updated] (LOG4J2-1963) Usage of braces in filePattern creates unexpected behaviors

[ https://issues.apache.org/jira/browse/LOG4J2-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Sazzadul Hoque updated LOG4J2-1963: - Description: Consider my following code: {quote}{code:java} import org.apache.logging.lo

[jira] [Updated] (LOG4J2-1963) Usage of braces in filePattern creates unexpected behaviors

[ https://issues.apache.org/jira/browse/LOG4J2-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Sazzadul Hoque updated LOG4J2-1963: - Description: Consider my following code: {quote}{code:java} import org.apache.logging.lo

[jira] [Updated] (LOG4J2-1963) Usage of braces in filePattern creates unexpected behaviors

[ https://issues.apache.org/jira/browse/LOG4J2-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Sazzadul Hoque updated LOG4J2-1963: - Description: Consider my following code: {quote}{code:java} import org.apache.logging.lo

[jira] [Created] (LOG4J2-1963) Usage of braces in filePattern creates unexpected behaviors

M Sazzadul Hoque created LOG4J2-1963: Summary: Usage of braces in filePattern creates unexpected behaviors Key: LOG4J2-1963 URL: https://issues.apache.org/jira/browse/LOG4J2-1963 Project: Log4j 2

Jenkins build is back to normal : log4net-trunk-tests #82

See