Autoware evaluation lab
A full Linux build of Autoware run by the official procedure, completed in 6h35m26s with all 621 target packages succeeding. The environment, the inputs and every failure along the way are recorded.
The project
Built the non-CUDA universe-devel target on a fresh Ubuntu Linux VM using the official Docker build procedure. Source commits and build inputs were pinned, and the environment and success criteria were recorded.
How it works
Check the build inputs
Official files for building the program were checked against a fixed version, and the conditions to match before execution were documented.
Plan independent builds
The planned procedure builds the program from the same inputs in independent environments without data left over from previous builds.
Plan how to compare the records
The plan records each run’s conditions, output and exit status so that results can be compared across environments.
The first phase completed one cold build with empty caches. The next planned phase repeats frozen inputs in independent environments with empty caches and workspaces; that comparison has not yet been run.
The log template records the environment, command, actual output, exit code, elapsed time and evidence location. Planning concerns and problems encountered during execution have separate records.
What the records show
The build completed in 6h35m26s. Its three colcon stages finished 55, 78 and 488 packages, for 621 successful packages with none failed or aborted. The build exited successfully; errors in the post-build check script were then fixed, and those checks passed on a cached rerun.
What this covers
This was one build on one machine. Reproducing it in an independent environment has not been done, and no driving or perception performance has been evaluated.