commit | e07f3174b1a7971e50f4fdda0363f24114331e8c | [log] [tgz] |
---|---|---|
author | Scott Todd <scott.todd0@gmail.com> | Wed Jun 26 16:25:03 2024 -0700 |
committer | GitHub <noreply@github.com> | Wed Jun 26 16:25:03 2024 -0700 |
tree | 2635a0365b2494e49301e27a77727c2836f24442 | |
parent | 2401be20d63aa2abb9ebf2a5a763a8384d10c205 [diff] |
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)  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.
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.
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!
See our website for more information.
Community meeting recordings: IREE YouTube channel
IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.