forked from bobjacobsen/JMRI
-
Notifications
You must be signed in to change notification settings - Fork 0
/
tests_jacoco.lcf
105 lines (83 loc) · 4.06 KB
/
tests_jacoco.lcf
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
# Log4J configuration file for running a 2nd pass of JUnit
# tests with logging turned on for JaCoCo coverage testing
# #############################################################
# Log4J configuration
# #############################################################
# Output is sent to system.err, generally a console window.
# The output info consists of relative time,
# category (usually name of the class doing the logging),
# priority, message text and thread name in
# that order.
# For the general syntax of property based configuration files see the
# documenation of org.apache.log4j.PropertyConfigurator.
# Valid priority names are FATAL, ERROR, WARN, INFO, DEBUG, and TRACE.
# The root category uses the appender called A1, which is set to log
# priority WARN and above. This is what's expected by the default
# message parsing in the JUnit tests.
# The root category is the only category that is given
# a default priority. All other categories do not have a default
# priority. in which case the priority is inherited from the
# hierarchy. See the end of the file for examples of how to
# control this at a finer level.
log4j.rootCategory= DEBUG, A1
# A1 is set to be a jmri.util.JUnitAppender which outputs to System.err.
# The JUnitAppender provides hooks used to test whether a given
# log message is expected or not, and whether ERROR messages have been logged.
log4j.appender.A1=jmri.util.JUnitAppender
# A1 writes to system.err to synchronize with e.g. exception traces
log4j.appender.A1.target=System.err
# To reduce the volume of logging stored while the tests are running,
# while still causing the debug code to run (isDebugEnabled will
# be true if log4j.rootCategory is set to DEBUG)
# Note: comment on this line if you want DEBUG output from specific categories below
log4j.appender.A1.Threshold=INFO
# A1 uses PatternLayout to control the format of the log messages.
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
# The conversion pattern uses format specifiers. For details, see
# the org.apache.log4j.PatternLayout Javadocs. To summarize:
#
# c category, e.g. %c{2} for right-most two tokens
# C classname of call (slow)
# d date, e.g. %d{ISO8601}, %d{ABSOLUTE}, %d{DATE}, %d{HH:mm:ss,SSS}
# or %d{dd MMM yyyy HH:mm:ss,SSS}
# F filename of call (slow)
# l location, JVM-dependent (extremely slow)
# m message
# M method name (slow)
# n line separator
# p priority
# r milliseconds elapsed
# t thread
# x nested diagnostic context
# % the sequence %% emits a single %
#
# Justification, padding and truncation can be controlled e.g. %-5.10p
# is left justified, at least 5 and no more than 10 characters wide
log4j.appender.A1.layout.ConversionPattern=%-5p - %m [%t] %c{4}.%M()%n
# R is set to output to a log file, but then not used in normal testing
log4j.appender.R=org.apache.log4j.FileAppender
log4j.appender.R.File=example.log
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%-5p - %m [%t] %c{2}.%M()%n
# Default Jetty server to only logging WARN since it can be verbose at points
log4j.category.org.eclipse.jetty=WARN
log4j.category.org.eclipse.jetty.server.handler=WARN
# Turning off logging for Java Xerces; emits WARNING messages during routine use
log4j.category.org.jdom2.transform=SEVERE
# Turning off logging for Java JMDNS; logs SEVERE and WARNING to j.u.l too routinely
log4j.category.com.strangeberry=OFF
log4j.category.javax.jmdns=OFF
# Needed for Jenkins I18N testing
log4j.category.jmri.util.I18NTest=DEBUG
# Needed for jmri.util.Log4JUtilTest
log4j.category.jmri.util.Log4JUtilTest = WARN
# Examples of changing priority of specific categories (classes, packages):
#
# log4j.category.jmri=DEBUG
# log4j.category.jmri.implementation=DEBUG
# log4j.category.jmri.jmrit.symbolicprog.tabbedframe=DEBUG
# log4j.category.jmri.jmrit.symbolicprog.tabbedframe.PaneProgPaneTest=DEBUG
# log4j.category.jmri.jmrit.symbolicprog.DecVariableValue=DEBUG
# log4j.category.jmri.jmrit.symbolicprog.LongAddrVariableValueTest=DEBUG
# log4j.category.jmri.jmrix.nce=DEBUG
# log4j.category.jmri.jmrix.nce.NceTrafficController=WARN