You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by GitBox <gi...@apache.org> on 2020/04/20 18:33:27 UTC

[GitHub] [hadoop-ozone] adoroszlai commented on issue #844: HDDS-3456. Acceptance test failures in OM HA and S3 Gateway

adoroszlai commented on issue #844:
URL: https://github.com/apache/hadoop-ozone/pull/844#issuecomment-616734345


   > Can you explain how this will fix disk out of space issue and what are these intermediate builds?
   
   `apache/ozone-build` is a pre-built image with all dependencies for Ozone ([source](https://github.com/apache/hadoop-docker-ozone/blob/build-latest/Dockerfile)).  The `buildenv` image is a throwaway image built for the CI run to workaround some environment/permission issue ([source](https://github.com/apache/hadoop-ozone/tree/master/.github/buildenv)).  The GitHub Action downloads the first image to build the second one.  It then builds Ozone in a container run with this image, and installs Ozone into local Maven repo.  All this happens in the _Run /./.github/buildenv_ step of the acceptance check.
   
   These Docker images are not needed for later steps of the acceptance check (ie. install Robot Framework and run tests).  The change thus removes these images from local image cache to free up some space, to avoid disk out of space issue.
   
   Removing Hadoop 3.1.2 image after the related test serves same purpose.


----------------------------------------------------------------
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org