[YANGTOOLS-729] yang-system-test: Even without -v, output is full of DEBUG messages Created: 22/Dec/16 Updated: 10/Apr/22 Resolved: 20/Feb/18 |
|
| Status: | Verified |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.0.0 |
| Type: | Bug | ||
| Reporter: | Vratko Polak | Assignee: | Igor Foltin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 7437 |
| Priority: | Lowest |
| Description |
|
The messages do not come from main(), but from parser (which uses slf4j as opposed to java.util.logging). This probably affects the performance, and also possible error lines may be hard to locate visually. An example output line: 1 [main] DEBUG org.opendaylight.yangtools.yang.parser.stmt.reactor.SourceSpecificContext - Source /home/jenkins/src/main/yang/experimental/odp/toaster-consumer-impl.yang started phase SOURCE_PRE_LINKAGE |
| Comments |
| Comment by Vratko Polak [ 22/Dec/16 ] |
|
Not sure if the messages go to stderr or stdout, as the suite redirects both to the same logfile. |
| Comment by Peter Kajsa [ 14/Mar/17 ] |
|
Low priority, therefore moving to Carbon SR1 |
| Comment by Igor Foltin [ 14/Sep/17 ] |