Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
Description
Found this in a local acceptance test run:
Start freon testing | FAIL | '2019-12-05 12:25:24,744 [main] INFO impl.MetricsConfig: Loaded properties from hadoop-metrics2.properties 2019-12-05 12:25:24,934 [main] INFO impl.MetricsSystemImpl: Scheduled Metric snapshot period at 10 second(s). 2019-12-05 12:25:24,935 [main] INFO impl.MetricsSystemImpl: ozone-freon metrics system started 2019-12-05 12:25:26,690 [main] INFO freon.RandomKeyGenerator: Number of Threads: 1 2019-12-05 12:25:26,691 [main] INFO freon.RandomKeyGenerator: Number of Volumes: 5. 2019-12-05 12:25:26,691 [main] INFO freon.RandomKeyGenerator: Number of Buckets per Volume: 5. 2019-12-05 12:25:26,691 [main] INFO freon.RandomKeyGenerator: Number of Keys per Bucket: 5. 2019-12-05 12:25:26,691 [main] INFO freon.RandomKeyGenerator: Key size: 10240 bytes 2019-12-05 12:25:26,691 [main] INFO freon.RandomKeyGenerator: Buffer size: 4096 bytes 2019-12-05 12:25:26,691 [main] INFO freon.RandomKeyGenerator: validateWrites : false [ Message content over the limit has been removed. ] ....util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) *************************************************** Status: Success Git Base Revision: e97acb3bd8f3befd27418996fa5d4b50bf2e17bf Number of Volumes created: 5 Number of Buckets created: 25 Number of Keys added: 125 Ratis replication factor: THREE Ratis replication type: RATIS Average Time spent in volume creation: 00:00:00,210 Average Time spent in bucket creation: 00:00:00,213 Average Time spent in key creation: 00:00:37,506 Average Time spent in key write: 00:01:42,157 Total bytes written: 1280000 Total Execution time: 00:02:31,516 ***************************************************' contains 'ERROR'
Need to check if Status: Success is true (ie. if keys were indeed successfully created), and if so, ERROR in output should make not the test failed.
Attachments
Issue Links
- links to