[
https://issues.apache.org/jira/browse/SOLR-13777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-13777:
----------------------------
Summary: contrib/ltr (and maybe others?) does not have test logging
configured correctly (was: contrib/ltr does not have test logging configured
correctly)
> contrib/ltr (and maybe others?) does not have test logging configured
> correctly
> -------------------------------------------------------------------------------
>
> Key: SOLR-13777
> URL: https://issues.apache.org/jira/browse/SOLR-13777
> Project: Solr
> Issue Type: Test
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
> Priority: Major
>
> i'm not 100% certain what magical properties/files are needed to get test
> logging setup consistently across all solr modules, but it doesn't seem to be
> in place for contrib/ltr.
> Consider this trivial example...
> {noformat}
> hossman@slate:~/lucene/dev/solr/contrib/ltr [j11] [master] $ ant test
> -Dtestcase=TestManagedFeatureStore -Dtests.showSuccess=true
> ...
> -test:
> [junit4] <JUnit4> says 你好! Master seed: CEC8592E171B132F
> [junit4] Executing 1 suite with 1 JVM.
> [junit4]
> [junit4] Started J0 PID(18975@slate).
> [junit4] Suite: org.apache.solr.ltr.store.rest.TestManagedFeatureStore
> [junit4] 2> ERROR StatusLogger No Log4j 2 configuration file found.
> Using default configuration (logging only errors to the console), or user
> programmatically provided configurations. Set system property 'log4j2.debug'
> to show Log4j 2 internal initialization logging. See
> https://logging.apache.org/log4j/2.x/manual/configuration.html for
> instructions on how to configure Log4j 2
> [junit4] OK 2.37s |
> TestManagedFeatureStore.testMissingFeatureReturnsNull
> [junit4] OK 0.66s |
> TestManagedFeatureStore.testDefaultFeatureStoreName
> [junit4] OK 0.48s | TestManagedFeatureStore.getInstanceTest
> [junit4] OK 0.34s | TestManagedFeatureStore.testFeatureStoreAdd
> [junit4] OK 0.35s | TestManagedFeatureStore.getInvalidInstanceTest
> [junit4] OK 0.35s | TestManagedFeatureStore.testFeatureStoreGet
> [junit4] Completed [1/1] in 5.71s, 6 tests
> ...
> {noformat}
> Notably this means that when tests in this module fail as part of jenkins
> builds, the only thing that gets logged is the final exception -- not any of
> the normal test scafolding (like what randomized SSL/clientAuth values were
> used) or logging leading up to that failure.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
