Too many log in test
Status
OTB logs are too big for GitLab CI console.
Reason
OTB logs are very heavy (for testing logs). There are two reasons for this :
- Even if the test is passing we have the full output of the logger. Which is not needed in my opinion. On nightly build you just want to see if the test is passing or not. You do not need to see logs from a passing test.
- There are some tests that have hundreds of line (sometimes error from a third parties, sometimes output of a kwl or else...) we should try to make them a little bit less verbose.
Solution
Few solutions I have in mind :
- Log only failing test, this can be done in the test kernel, logger should not flush unless an option in test line is given.
- Investigate on tests that output a lot of logs
List of very verbose tests
- apTvClComputeOGRLayersFeaturesStatistics
- apTvClSVMVectorClassifier
- apTvHyHyperspectralUnmixing_[UCLS/NCLS]
- apTvPrGenerateRPCSensorModel
- apTvPrRefineSensorModel
- apTvUtConcatenateVectorData
- ioTuGDALImageIOCanRead_PCI
- ioTuGDALImageIOCanRead_COSMOSKYMED[/2/3]
- ioTvOtbVectorImageTest[COSMOSKYMED/Spot5]
- raTvSurfaceAdjacencyEffectCorrectionSchemeFilter
- feTvImageToEdgePathFilterBis
- coTuPathListToHistogramGenerator
- prTvSensorModel_[**]
- siTuSatelliteRSR
- siTuReduceSpectralResponse
- siT[u/v]ReduceSpectralResponseReflectanceMode
- siTuSpectralResponse
- bfTvConcatenateVectorDataFilter
- feTeHarrisExampleTest
- siTvProsailModelExampleTest
Edited by Antoine Regimbeau