Abstract
The ART (ATLAS Release Tester) system is designed to run test jobs on the Grid after a nightly release of the ATLAS offline software has been built. The choice was taken to exploit the Grid as a backend as it offers a huge resource pool, suitable for a deep set of integration tests, and running the tests could be delegated to the highly scalable ATLAS production system (PanDA). The challenge of enabling the Grid as a test environment is met through the use of the CVMFS file system for the software and input data files. Test jobs are submitted to the Grid by the GitLab Continuous Integration (gitlab-ci) system, which itself is triggered at end of a release build. Jobs can be adorned with special headers that inform the system how to run the specific test, allowing many options to be customised. The gitlab-ci system waits for exit status and output files are copied back from the Grid to an EOS area accessible by users. All gitlab-ci jobs run in ART’s virtual machines, using docker images for their ATLAS setup. ART jobs can be tracked by using the PanDA system. ART can also be used to run short test jobs locally. It uses the same ART command-line interface, where the backend is replaced to access a local machine for job submission rather than the Grid. This allows developers to ensure their tests work correctly before adding them to the system. In both the Grid and local machine options, running and result copying are completely parallelized. ART is written in python, complete with its own local and Grid tests to give approximately 90% code coverage of the ART tool itself. ART has been in production for one year and fully replaces and augments the former ATLAS testing system.
Highlights
The offline software of the ATLAS experiment [1], Athena [2, 3], is jointly developed by more than hundred members of the ATLAS collaboration
This paper focuses on the ART (ATLAS Release Tester) [5] testing system: ART tests can be relatively heavy, involving the processing of hundreds or even thousands of events
The tar file of each job consists of output files that are specified in each test script via the art-output header
Summary
The offline software of the ATLAS experiment [1], Athena [2, 3], is jointly developed by more than hundred members of the ATLAS collaboration. This collaborative effort is enabled by modern software infrastructure like git for version control, continuous integration and nightly builds [4]. This paper focuses on the ART (ATLAS Release Tester) [5] testing system: ART tests can be relatively heavy, involving the processing of hundreds or even thousands of events. They are run on every nightly build. The results are checked by release coordinators to spot possible regressions with respect to a fixed reference or a previous nightly release
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
