Documentation

Overview

This site displays test results for ROCm packages on Ubuntu and is automatically updated after each test run.

How to access the packages?

Packages listed here can be accessed via apt directly, since Ubuntu 26.04. If you would like to access the development version of these packages, please see the instructions in this section.

Test Results

The main page shows the latest test results from automated test runs.

Logs

Test logs for each run can be found in rocm-qa repository in logs branch.

How to interpret the tables?

Test results tables consists of “Test Suite”, “System” and “Result” columns.

Test Suite: Name of the test suite we run using the package.

autopkgtest: Simply runs autopkgtests defined for the debian package. In addition to the usual “FAIL” status of autopkgtest, if a package doesn’t have any autopkgtest, then the result will be marked as “FAIL” as well.

level-one: Placeholder name for a test suite that will run basic heartbeat tests with a set of applications (details to be added).

System: Name of the system the test ran on.

Result: Result of the test run either FAIL or PASS. If ‘ERROR’ seen, that means there was an infrastructure error while running that test.

Development PPA

ROCm packaging team in Canonical maintains the development of ROCm packages under the name of ~bullwinkle-team in Launchpad.

If the packages already available in the Ubuntu archive are not enough for you and you want to use packages that are still in the development stage, you can use the following instructions to enable the PPA in your system and install the specific package you want from the PPA.

sudo add-apt-repository ppa:bullwinkle-team/rocm-devel-21

# Install all rocm packages
sudo apt install rocm-dev
# Or only install what you need
sudo apt install hipcc

See the development PPAs below:

• ppa:rocm-devel-21 : ROCm development archive which holds packages built against upstream LLVM-21

Badges

Dynamic badges are available for each package at: /badges/<package-name>.json

These badges follow the Shields.io endpoint schema and can be used in README files or other documentation.