From 4babb0f39f7e37743810510985e4473d13adc655 Mon Sep 17 00:00:00 2001 From: Marius Brehler Date: Mon, 23 Sep 2024 09:18:52 +0000 Subject: [PATCH] Document requirements for `torch_mlir_e2e_test` This documents which CMake options must be set to be able to use `torch_mlir_e2e_test`, required e.g. for `projects/pt1/tools/e2e_test.sh`. Makes progress on #3696. Closes #3719. --- docs/development.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/development.md b/docs/development.md index 771c4fcbef0e..57001bd60689 100644 --- a/docs/development.md +++ b/docs/development.md @@ -396,6 +396,8 @@ Torch-MLIR has two types of tests: a homegrown testing framework (see `projects/pt1/python/torch_mlir_e2e_test/framework.py`) and the test suite lives at `projects/pt1/python/torch_mlir_e2e_test/test_suite/__init__.py`. + The tests require to build with `TORCH_MLIR_ENABLE_PYTORCH_EXTENSIONS` (and + the dependent option `TORCH_MLIR_ENABLE_JIT_IR_IMPORTER`) set to `ON`. 2. Compiler and Python API unit tests. These use LLVM's `lit` testing framework. For example, these might involve using `torch-mlir-opt` to run a pass and