https://git.lavasoftware.org/lava/ci-images/merge_requests/4

I've had problems getting Docker in Docker working on arm64. As the second main architecture for LAVA, I was looking at how to build arm64 docker images inside GitLab CI - using the same methods as the amd64 builds. A number of issues resulted: The DinD base images are complex and it's not obvious how to build an arm64 docker image which can run in privileged mode and build other docker images inside it - certainly not within our existing GitLab CI. The available arm64 hardware has lots of cores but is slow at single threaded operations. I manually built the arm64 docker images to run the unit tests outside of the GitLab CI, even with -n 18 support to use 18 of the 24 cores, it is still too slow to use on every change to every merge request. That then means that automatically building the arm64 docker images is less of an issue - we can simply run some arm64 tests when a git tag is pushed. The overall issue will be kept under review but for now, we'll be fine with manually rebuilding arm64 dockers from time to time and running arm64 tests only on tags. So the WIP for ci-images has been abandoned and the WIP on lava will be lower priority.

Other merge requests were discussed too:

https://git.lavasoftware.org/lava/lava/merge_requests/103 The XML_RPC support will gain documentation on how to use the allow_none setting in XMLRPC clients to help keep the newer XML_RPC function output consistent.

https://git.lavasoftware.org/lava/lava/merge_requests/14 The skip_timeout support will be tweaked to use a boolean flag in the timeout block of the test action and the contribution guide updated to show a distinction that tags should relate to user/device data and elements relating directly to the code should use the structures instead.

https://git.lavasoftware.org/lava/lava/merge_requests/12

Excessive messages will be changed to handle the trim inside the exception handler.

These merge requests will get updates in the next few days.

https://git.lavasoftware.org/lava/lava/merge_requests?scope=all&utf8=%E2...

There are a number of merge requests tagged with the 2018.10 milestone - these are the ones we are trying to get merged before making a new upstream release of LAVA.

Finally, a reminder, this list is intended for developers of LAVA to support discussion of changes before or after a merge request is opened. Please abide by the Code of Conduct and Contribution Guide.

https://www.lavasoftware.org/code-of-conduct.html

https://master.lavasoftware.org/static/docs/v2/contribution-intro.html