pvary edited a comment on pull request #1789: URL: https://github.com/apache/iceberg/pull/1789#issuecomment-731214967
> Looks like the log is too long with this enabled: > > ``` > This file has been truncated. View the full logs in the ... menu once the check is completed. > ``` It is still possible to see the logs by downloading them starting from the `...` from the top right corner of the Details screen. But I absolutely agree that this is not ideal since we might need to download the full logs to find the failures. That is why I followed up on your suggestion below. > Maybe we can output logs to files for each module and fetch them when we need them? We can look into getting the files produced. I was able to come up with a solution where I put the output of the tests for subproject specific files, and added them as an artifacts for the builds in case of a failure. This archive is accessible under the `Artifacts` button. See: https://github.com/apache/iceberg/runs/1431325389 (intentionally created some test failures) Sample output (build/testlogs/iceberg-parquet.log): ``` -------- - Test log for: Test testRowGroupSizeConfigurableWithWriter(org.apache.iceberg.parquet.TestParquet) -------- StdErr log4j:WARN No appenders could be found for logger (org.apache.hadoop.util.NativeCodeLoader). StdErr log4j:WARN Please initialize the log4j system properly. StdErr log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. -------- - Test log for: Test testListProjection(org.apache.iceberg.avro.TestParquetReadProjection) -------- StdErr [Test worker] INFO org.apache.parquet.hadoop.InternalParquetRecordReader - RecordReader initialized will read a total of 1 records. StdErr [Test worker] INFO org.apache.parquet.hadoop.InternalParquetRecordReader - at row 0. reading next block StdErr [Test worker] INFO org.apache.parquet.hadoop.InternalParquetRecordReader - block read in memory in 1 ms. row count = 1 ``` Since I think this could be useful for every time we run the tests I have configured this logging not only for CI runs but for general test runs as well - some might disagree so please check this. Thanks, Peter ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
