[
https://issues.jboss.org/browse/JBTM-2639?page=com.atlassian.jira.plugin....
]
Michael Musgrove edited comment on JBTM-2639 at 3/14/16 7:34 AM:
-----------------------------------------------------------------
Examples of tests tjhat show excessive log output in the linked CI job are:
./txcore_lockrecord/LockRecord_Thread_Test032b/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test030a/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test031b/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test042a/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test034a/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test036a/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test031a/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test035b/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test034b/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test033b/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test032a/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test030b/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test036b/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test033a/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test035a/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test042b/client_0_output.txt
./jtatests01/JTATests01_Test006/client_0_output.txt
The excessive logging seems to be for similar tests. In the second ci job failure we
have:
find testoutput -xdev -type f -size +400M
testoutput/txcore_lockrecord/LockRecord_Thread_Test032b/client_0_output.txt
testoutput/txcore_lockrecord/LockRecord_Thread_Test031b/client_0_output.txt
testoutput/txcore_lockrecord/LockRecord_Thread_Test034a/client_0_output.txt
testoutput/txcore_lockrecord/LockRecord_Thread_Test008a/client_0_output.txt
testoutput/txcore_lockrecord/LockRecord_Thread_Test031a/client_0_output.txt
testoutput/txcore_lockrecord/LockRecord_Thread_Test034b/client_0_output.txt
testoutput/txcore_lockrecord/LockRecord_Thread_Test032a/client_0_output.txt
testoutput/txcore_lockrecord/LockRecord_Thread_Test012b/client_0_output.txt
testoutput/txcore_lockrecord/LockRecord_Thread_Test035a/client_0_output.txt
testoutput/txcore_lockrecord/LockRecord_Thread_Test012a/client_0_output.txt
testoutput/jtatests01/JTATests01_Test006/client_0_output.txt
was (Author: mmusgrov):
Examples of tests tjhat show excessive log output in the linked CI job are:
./txcore_lockrecord/LockRecord_Thread_Test032b/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test030a/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test031b/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test042a/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test034a/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test036a/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test031a/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test035b/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test034b/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test033b/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test032a/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test030b/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test036b/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test033a/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test035a/client_0_output.txt
./txcore_lockrecord/LockRecord_Thread_Test042b/client_0_output.txt
./jtatests01/JTATests01_Test006/client_0_output.txt
Setting QA_TRACE=0 does not disable trace logging in all tests
--------------------------------------------------------------
Key: JBTM-2639
URL:
https://issues.jboss.org/browse/JBTM-2639
Project: JBoss Transaction Manager
Issue Type: Bug
Components: Testing
Affects Versions: 5.3.1.Final
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 5.next
Occasionally some of the QA journal tests fail because of excessive logging (the job is
producing over 30G of log output). I tried setting QA_TRACE=0 in the Jenkins job config
but some tests are still producing trace output.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)