Google Git
Sign in
opensecura / 3p / openxla / iree / c87eafe3acd5319caa106d3bcc6488b87aedb8ea
commitc87eafe3acd5319caa106d3bcc6488b87aedb8ea[log] [tgz]
authorScott Todd <scott.todd0@gmail.com>Wed Mar 06 14:13:02 2024 -0800
committerGitHub <noreply@github.com>Wed Mar 06 14:13:02 2024 -0800
tree8655e0e4c09b45463168d51757d2975e7c4b6bbe
parentbb9409f32ecd0e76090dfefa33879a41f48b4cf2 [diff]
Update external test suite version pin and XFAIL sets. (#16675)

Progress on https://github.com/openxla/iree/issues/16372

This includes the latest updates to the external test suite (currently
only ONNX test cases):

* Regenerated test cases using IREE's latest version of torch-mlir
* Regenerated test cases by first converting them to ONNX opset version
17+
* Fixed XFAIL behavior to actually XFAIL/XPASS by turning on "strict"
mode and using an API that does what it claims (good job, pytest)


Before: `238 passed, 809 xfailed in 15.77s`
After: `344 passed, 887 xfailed in 18.06s`

Now that XFAIL/XPASS actually works, we may start seeing tests newly
passing on presubmit here, though I'm aware of some ergonomics issues in
updating the XFAIL lists that could be fixed:

* Ideally the CI jobs would give you a config file to copy/paste if you
want to accept the run results
* Right now the "compile" and "run" steps are mixed together, so it
sometimes takes a few attempts of moving between
`expected_compile_failures` and `expected_run_failures` before pytest is
happy
6 files changed
tree: 8655e0e4c09b45463168d51757d2975e7c4b6bbe
  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. .gitignore
  23. .gitmodules
  24. .yamllint.yml
  25. AUTHORS
  26. BUILD.bazel
  27. CITATION.cff
  28. CMakeLists.txt
  29. configure_bazel.py
  30. CONTRIBUTING.md
  31. LICENSE
  32. README.md
  33. 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

License

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