-
Notifications
You must be signed in to change notification settings - Fork 581
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Move benchmark config generation to build_e2e_test_artifacts (#13291)
When working on #13273, I noticed that benchmark configs and modules are uploaded in 3 different jobs. These artifacts can be uploaded to different GCS dirs when some of them are re-run due to failures (because re-run jobs will create [GCS_DIR with new run attempts](https://github.com/openxla/iree/blob/main/.github/workflows/benchmark_compilation.yml#L44-L50)). As a result, users might not be able to download all benchmark artifacts from a single GCS dir URL, which can be confusing. This PR changes the workflow to generate all benchmark modules and configs in `build_e2e_test_artifacts` to avoid such issue. All files are uploaded to `${GCS_URL}/e2e-test-artifacts`, a single path to download all benchmark artifacts. Besides the reason above, I think during the CMake build we should generate the benchmark configs under `${IREE_BUILD_DIR}/e2e_test_artifacts` instead of calling `export_benchmark_config.py` separately. There are some questions about how to pass the benchmark presets/filters through CMake configuration, so I decided to defer that as the next step.
- Loading branch information
Showing
6 changed files
with
49 additions
and
66 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters