adoroszlai opened a new pull request, #11938:
URL: https://github.com/apache/ozone/pull/11938

   ## What changes were proposed in this pull request?
   
   Kubernetes tests run Rebot (combining multiple Robot test reports and 
converting to HTML) in Docker.  This requires the `ozone-runner` image to be 
downloaded:
   
   ```
   2026-10-08T06:39:57.4177075Z Unable to find image 
'ghcr.io/apache/ozone-runner:20260922-1-jdk25' locally
   ...
   2026-10-08T06:40:14.8873088Z Status: Downloaded newer image for 
ghcr.io/apache/ozone-runner:20260922-1-jdk25
   ```
   
   But the image is already available in the Kubernetes cluster.  Rebot can be 
run in one of the pods.
   
   There are two Rebot runs:
   1. 
[`combine_reports`](https://github.com/apache/ozone/blob/a6332fb59879b80615b9233e953d6813d03ae7a8/hadoop-ozone/dist/src/main/k8s/examples/testlib.sh#L191)
 during `post_run` of each environment, while the cluster is still running
   2. last step of 
[`test-all.sh`](https://github.com/apache/ozone/blob/a6332fb59879b80615b9233e953d6813d03ae7a8/hadoop-ozone/dist/src/main/k8s/examples/test-all.sh#L56),
 no cluster available at this time
   
   This PR changes (1) to run in a pod, and removes (2), since each environment 
is tested separately after HDDS-16714.  The container mounts a local temp dir 
at `/robot` to save outputs and generate report.
   
   https://issues.apache.org/jira/browse/HDDS-16784
   
   ## How was this patch tested?
   
   CI:
   https://github.com/adoroszlai/ozone/actions/runs/41862457162
   
   ```
   Output:  /robot/output.xml
   Log:     /robot/log.html
   renamed '/tmp/robot-data-bUG2qO/log.html' -> 'result/log.html'
   renamed '/tmp/robot-data-bUG2qO/output.xml' -> 'result/output.xml'
   ```
   
   Downloaded `kubernetes` artifacts and checked `log.html`.
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to