tree 8f551383b3381b43916a9adceb12e614032f4383
parent 7a86df40bca9ccb5ae84a467922063de8d414a96
author Jerry Wu <cheyuw@google.com> 1682472993 +0000
committer GitHub <noreply@github.com> 1682472993 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJkSIAhCRBK7hj4Ov3rIwAAMf4IAIwFvJsEGgTH3LyO90xwutby
 a3fegqADROQo69EvuDL48NWzDIMsE+9NidFfdsgo8NtN2AxasYD1RP0dwsnfzlJy
 puq6y2tekkQ7v8eVRjwNaZMfZFNvRdOD28km3FGy7yqUQkz15lGUzhwEAMknydO7
 bBCjXdRal2n5atKeJHSMJoNNtUz+RPEnC+7O+RvuqvRMVt2Bl0pzyNJeJx4EmwfU
 81Cg8rIbca+38djuXObWsVgdA59BETi5E4jI4EyD/I3c1z2C34Ca4rYE0OXIEpi2
 GzIoUj6qw22E94eVsAvHhINl0c4WsO3I5+vhSnnxcDe4jZ3uoHrLMzZagqhsMFM=
 =e6Dn
 -----END PGP SIGNATURE-----
 

Move benchmark config generation to build_e2e_test_artifacts (#13291)

When working on https://github.com/openxla/iree/pull/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.