Tamara Dahlgren

@chrisrichardson @garth-wells Did you want to take another look before this PR is merged?

Will defer merge decision to give maintainers a chance to comment.

Looks like CI pipeline has hung.

@spackbot run pipeline

@zackgalbreath @tgamblin @becker33 (Update: Adding `VendorString` attribute to the `Site` element per an off-line discussion.) (Update: Replaced generated output for the same package as of commit XYZ.) Commit ec03ceb generated...

Since we want to know if a package does not have tests to run, I created a dummy test part so we can flag/track such packages (starting with commit 2c1ac7c)....

Interesting test failures in what appear to be a section untouched by this PR (Updated example below): ``` _______________________________ test_config_edit _______________________________ [2540](https://github.com/spack/spack/runs/5236546178?check_suite_focus=true#step:6:2540) [2541](https://github.com/spack/spack/runs/5236546178?check_suite_focus=true#step:6:2541) def test_config_edit(): [2542](https://github.com/spack/spack/runs/5236546178?check_suite_focus=true#step:6:2542) """Ensure `spack config edit`...

Testing outputs are being loaded to https://my.cdash.org/index.php?project=Spack+Pipelines. Current results for tests look like: 

Ugh. `gptune` in the `e4s-pr-build` is the only one failing (again).

And, according to the CDash table (https://cdash.spack.io/index.php?project=debugging), there are only 3 packages without test results: ``` Cloud Gitlab Infrastructure (uo-gilgamesh) | [email protected]%[email protected] arch=linux-ubuntu18.04-x86_64 (Spack E4S CI Testing) Cloud Gitlab Infrastructure...