Drop Vulkan driver tests from `tools/test/`. (#15912)

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

This directory is for tests of the core project, so we should support
the tests on as broad a range of targets as possible. Driver-specific
tests (including ones that require specific hardware) are still useful,
but this monolithic MLIR lit test suite is not the place for them.

Without a change like this, https://github.com/openxla/iree/pull/15837
would skip the `tools/test/` test suite in the `test_all` job, since
SwiftShader is no longer used as a software implementation of Vulkan and
all Vulkan tests are skipped on CPU-only machines:
```
# Before:
iree/tools/test                                                       =  59.68 sec*proc (22 tests)

# Drop SwiftShader, without this change:
iree/tools/test                                                       =   0.27 sec*proc (1 test)

# With this change:
iree/tools/test                                                       =  49.66 sec*proc (22 tests)
```
(sample logs:
[before](https://github.com/openxla/iree/actions/runs/7198521417/job/19608693537#step:6:3090),
[drop SwiftShader without this
change](https://github.com/openxla/iree/actions/runs/7171350678/job/19526876959?pr=15837#step:6:2813),
[with this
change](https://github.com/openxla/iree/actions/runs/7200086847/job/19613475932?pr=15912#step:6:3089))
6 files changed
tree: c47953c685f04a1135f32a3543bbea97c3c447fc
  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

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.