PSA: Bazel building of IREE TensorFlow integration e2e tests being removed

[Stella Laurenzo]

We've updated the instructions for using Python and TensorFlow builds: https://google.github.io/iree/get-started/getting-started-python

The patches that enable this new build integration are coming in ~today.

In short:

• Things like "bazel test integrations/tensorflow/e2e/..." are being removed (as is all Bazel support for python builds)
• CMake/Ninja is now used to build the whole project, enabling python and TensorFlow compilation via "-DIREE_BUILD_PYTHON_BINDINGS=ON -DIREE_BUILD_TENSORFLOW_COMPILER=ON".
• This still uses bazel under the covers to build the TensorFlow compiler frontend but exports the resultant binaries to the CMake/Ninja side vs requiring everything to be built under Bazel.
• Once built and the PYTHONPATH set (or the setup.py script run), python scripts/tests can be run with no further building (i.e. you can just run python scripts in the integrations/tensorflow/e2e directory).
• We will be re-adding CTest rules for most of these tests in the coming days, at which point, CTest will be authoritative.

There are quite a few moving parts to get this rolled out properly and we're trying not to break things. Reach out if you are having issues.

- Stella

[Phoenix Meadowlark]

We've updated the OSS CI to no longer tests bindings/... and integrations/... with Bazel. 

The bindings are still tested using CMake, but there is currently no test coverage from integrations/..., so it may be easier to accidentally submit bugs for a short while.

--
You received this message because you are subscribed to the Google Groups "iree-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iree-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/iree-discuss/CAGS7HzYf47EaADsxk_VPKbi5g4M0CETHMsE1ty9dNUxcX2f4gA%40mail.gmail.com.