Fix build_package.yml by giving uploads unique names. (#17746)

https://github.com/iree-org/iree/pull/17705 updated this workflow to
artifacts v4, which no longer allows multiple jobs to upload to the same
artifact name. Last night the `build_package.yml` workflow failed with
`Failed to CreateArtifact: Received non-retryable error: Failed request:
(409) Conflict: an artifact with this name already exists on the
workflow run`. The fix here is taken from
https://github.com/actions/upload-artifact?tab=readme-ov-file#not-uploading-to-the-same-artifact.

Previous success:
https://github.com/iree-org/iree/actions/runs/9660426654
* Note: 1.02GB 'artifact' (combined with all .whl files in the same zip)

![image](https://github.com/iree-org/iree/assets/4010439/5fc400c2-51d7-47d5-b190-9f03bbea5081)

Latest failure: https://github.com/iree-org/iree/actions/runs/9677626043
* Note: 33KB 'artifact' from `linux-x86_64 :: Build
py-tf-compiler-tools-pkg Package`

skip-ci: untested. Could try with
https://github.com/iree-org/iree/actions/workflows/oneshot_candidate_release.yml
but I'm leaning towards testing in prod for this. If this doesn't work
we can revert back to artifacts v3.
1 file changed
tree: 2635a0365b2494e49301e27a77727c2836f24442
  1. .devcontainer/
  2. .github/
  3. build_tools/
  4. compiler/
  5. docs/
  6. experimental/
  7. integrations/
  8. lib/
  9. llvm-external-projects/
  10. runtime/
  11. samples/
  12. tests/
  13. third_party/
  14. tools/
  15. .bazel_to_cmake.cfg.py
  16. .bazelignore
  17. .bazelrc
  18. .bazelversion
  19. .clang-format
  20. .dockerignore
  21. .git-blame-ignore-revs
  22. .gitattributes
  23. .gitignore
  24. .gitmodules
  25. .pre-commit-config.yaml
  26. .yamllint.yml
  27. AUTHORS
  28. BUILD.bazel
  29. CITATION.cff
  30. CMakeLists.txt
  31. configure_bazel.py
  32. CONTRIBUTING.md
  33. LICENSE
  34. MAINTAINERS.md
  35. README.md
  36. RELEASING.md
  37. WORKSPACE
README.md

IREE: Intermediate Representation Execution Environment

IREE (Intermediate Representation Execution Environment, pronounced as “eerie”) is an MLIR-based end-to-end compiler and runtime that lowers Machine Learning (ML) models to a unified IR that scales up to meet the needs of the datacenter and down to satisfy the constraints and special considerations of mobile and edge deployments.

See our website for project details, user guides, and instructions on building from source.

CI Status IREE Discord Status

Project Status

IREE is still in its early phase. We have settled down on the overarching infrastructure and are actively improving various software components as well as project logistics. It is still quite far from ready for everyday use and is made available without any support at the moment. With that said, we welcome any kind of feedback on any communication channels!

Communication Channels

Related Project Channels

  • MLIR topic within LLVM Discourse: IREE is enabled by and heavily relies on MLIR. IREE sometimes is referred to in certain MLIR discussions. Useful if you are also interested in MLIR evolution.

Architecture Overview

IREE Architecture IREE Architecture

See our website for more information.

Presentations and Talks

Community meeting recordings: IREE YouTube channel

  • 2021-06-09: IREE Runtime Design Tech Talk (recording and slides)
  • 2020-08-20: IREE CodeGen: MLIR Open Design Meeting Presentation (recording and slides)
  • 2020-03-18: Interactive HAL IR Walkthrough (recording)
  • 2020-01-31: End-to-end MLIR Workflow in IREE: MLIR Open Design Meeting Presentation (recording and slides)

License

IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.