Reproducing Pull Request Testing Errors
If the failure you are seeing shows up in the "checks" section of your Pull Request under AT2 (e.g. check name is AT2/gcc10-openmpi4), you are on the correct page.
If the failure shows up in a comment on the Pull Request, you will need to see this page instead, as that build runs through the legacy testing system (AutoTester1).
Information about the job runs is located in the artifacts for a given action:
Build environments are managed using container images. You can see the image ID used for a check in the summary page of that check, and in the console output of that check.
Once the container is running, the GenConfig tool and its associated subcomponents are used to finalize any last environment settings. GenConfig requires a key to know what values to load, which is stored in a file in the job artifacts called genconfig_build_name.txt. It is also visible in the job console output, as well as the job summary.
# This assumes that you have a clone of Trilinos at ~/Trilinos and that it is checked out to the correct git revision
podman run --rm -it --mount type=bind,src=~/Trilinos,dst=/root/Trilinos <registry-image>
cd /root/Trilinos
./packages/framework/get_dependencies.sh
mkdir build
cd build
source ../packages/framework/GenConfig/gen-config.sh --force --cmake-fragment pr.cmake <genconfig-build-id> ..
The GenConfig tool populates an initial CMake cache file that contains most of the settings used for a build of Trilinos. It uses an input file packages/framework/ini-files/config-specs.ini, where you can see the input directives that correspond to all settings (e.g. which tests are disabled for which builds). The cache file (pr.cmake here) can also be viewed to see all of the settings that will be ingested by CMake, and can be easier to read because it is "flat" (no inheritance as there would be in configs-specs.ini).
The other piece of information needed is the Trilinos packages to enable, which is automatically determined based off of which files in the repository have changed. That information is available in a file located in the job artifacts, entitled packageEnables.cmake.
There are sometimes other settings that are specific to the user's machine (e.g. the number of GPUs to use on a given machine (default 1), or the number of tests to run per GPU (default 8)). These options can be seen in the configure_command.txt file in the job artifacts, and can be passed on the command line via the standard CMake syntax depending on your machine configuration.
cd /root/Trilinos/build
cmake -C pr.cmake -C packageEnables.cmake ..
ninja
ctest