buildbot exception in ASF Buildbot on log4j2-nightly

The Buildbot has detected a build exception on builder log4j2-nightly while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/log4j2-nightly/builds/177 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: lares_ubuntu Build Reason: The Nightly sch

Fwd: buildbot exception in ASF Buildbot on log4j2-nightly

How can we tell what's wrong? Gary  Original message From: build...@apache.org Date:11/29/2014 03:17 (GMT-05:00) To: log4j-dev@logging.apache.org Cc: Subject: buildbot exception in ASF Buildbot on log4j2-nightly The Buildbot has detected a build exception on builder log4j2

[jira] [Commented] (LOG4J2-908) JSONLayout doesn't add a comma between log events

[ https://issues.apache.org/jira/browse/LOG4J2-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228753#comment-14228753 ] Gary Gregory commented on LOG4J2-908: - Ate you setting complete = true ? > JSONLayout

[jira] [Commented] (LOG4J2-908) JSONLayout doesn't add a comma between log events

[ https://issues.apache.org/jira/browse/LOG4J2-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228764#comment-14228764 ] Konstantinos Liakos commented on LOG4J2-908: Yes, I am setting , and not only

Re: buildbot exception in ASF Buildbot on log4j2-nightly

:-) I completely agree. Sent from my iPhone > On 2014/11/29, at 21:18, Gary Gregory wrote: > > How can we tell what's wrong? > > Gary > > > Original message > From: build...@apache.org > Date:11/29/2014 03:17 (GMT-05:00) > To: log4j-dev@logging.apache.org > Cc: > Subject:

Re: buildbot exception in ASF Buildbot on log4j2-nightly

ah there is more info: http://ci.apache.org/builders/log4j2-nightly/builds/177/steps/compile_1/logs/stdio Gary On Sat, Nov 29, 2014 at 7:18 AM, Gary Gregory wrote: > How can we tell what's wrong? > > Gary > > > Original message > From: build...@apache.org > Date:11/29/2014 03:

[jira] [Commented] (LOG4J2-834) NoClassDefFoundError in ThrowableProxy

[ https://issues.apache.org/jira/browse/LOG4J2-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228771#comment-14228771 ] Gary Gregory commented on LOG4J2-834: - When I apply the patch, the ForceNoDefClassFoun

[jira] [Comment Edited] (LOG4J2-834) NoClassDefFoundError in ThrowableProxy

[ https://issues.apache.org/jira/browse/LOG4J2-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228771#comment-14228771 ] Gary Gregory edited comment on LOG4J2-834 at 11/29/14 2:22 PM: -

[jira] [Updated] (LOG4J2-834) NoClassDefFoundError in ThrowableProxy

[ https://issues.apache.org/jira/browse/LOG4J2-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thiago Kronig updated LOG4J2-834: - Attachment: InexistentInterface.java ForceNoDefClassFoundError.java > NoClassDefFo

[jira] [Commented] (LOG4J2-834) NoClassDefFoundError in ThrowableProxy

[ https://issues.apache.org/jira/browse/LOG4J2-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228817#comment-14228817 ] Thiago Kronig commented on LOG4J2-834: -- I did the following steps to build the patch:

Re: buildbot exception in ASF Buildbot on log4j2-nightly

I am not sure why the nightly build would be building the site. Yesterday when i saw this I performed a log4j build and it failed with the log below. I can’t really tell what is wrong with the MarkerTest just by looking. T E S T S --- Running

[jira] [Updated] (LOG4J2-901) Update docs for SyslogAppender: "No structured id name was supplied"

[ https://issues.apache.org/jira/browse/LOG4J2-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-901: Summary: Update docs for SyslogAppender: "No structured id name was supplied" (was: SyslogAppender

[jira] [Resolved] (LOG4J2-901) Update docs for SyslogAppender: "No structured id name was supplied"

[ https://issues.apache.org/jira/browse/LOG4J2-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-901. - Resolution: Fixed Fix Version/s: 2.2 Docs updated. Site needs to be regenerated. > Update

Re: buildbot exception in ASF Buildbot on log4j2-nightly

I see this locally. It seems that a lot of tests do not clean up after themselves. So might have to run in their own VMs... On Sat, Nov 29, 2014 at 11:58 AM, Ralph Goers wrote: > I am not sure why the nightly build would be building the site. > > Yesterday when i saw this I performed a log4j bui

[jira] [Resolved] (LOG4J2-834) NoClassDefFoundError in ThrowableProxy

[ https://issues.apache.org/jira/browse/LOG4J2-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-834. - Resolution: Fixed Fix Version/s: 2.2 I added a test for this ticket just like the one attac

[jira] [Commented] (LOG4J2-902) Log4j-2-Bridge incompatible to OWSAP ESAPI framework

[ https://issues.apache.org/jira/browse/LOG4J2-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228867#comment-14228867 ] Gary Gregory commented on LOG4J2-902: - So we can close as won't fix or is there some e

[jira] [Commented] (LOG4J2-890) log4j-web-2.1 doesn't work under JBOSS EAP 6.2

[ https://issues.apache.org/jira/browse/LOG4J2-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228870#comment-14228870 ] Gary Gregory commented on LOG4J2-890: - It looks like the Wildfly bug will be fixed whe

Bug report for Log4j [2014/11/30]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned