[
https://issues.jboss.org/browse/WFCORE-3311?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-3311:
------------------------------------------
It's possible your ConsoleHandler change bypassed the stdio gymnastics the test uses
to be able to track what the output is. There may not be any way to guard against that in
the test. Maybe some sort of reversal thing could work in a test; i.e. not checking that
nothing appears, but rather ensuring that with a different setup something appears. If the
console output is going directly to the primordial stdout/err then it wouldn't be
coming through the streams the test sets up. But... I expect there are already tests like
that too that didn't fail.
embedded server --std-out=discard still causes log output to be
shown
---------------------------------------------------------------------
Key: WFCORE-3311
URL:
https://issues.jboss.org/browse/WFCORE-3311
Project: WildFly Core
Issue Type: Bug
Reporter: Ken Wills
Assignee: James Perkins
[disconnected /] embed-server --std-out=discard
10:27:43,671 INFO [org.jboss.modules] (CLI command executor) JBoss Modules version
1.6.1.Final
10:27:43,698 INFO [org.jboss.as] (MSC service thread 2-8) WFLYSRV0049: WildFly Core
4.0.0.Alpha1-SNAPSHOT "Kenny" starting
... etc
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)