nanjeshramesh commented on PR #11735: URL: https://github.com/apache/nifi/pull/11735#issuecomment-5977168248
Thanks @MikeThomsen, you were right. The new Python test imports `nifiapi.properties`, which imports `py4j.protocol`, and py4j isn't on the PYTHONPATH for the `nifi-python-extension-api` module in CI (it was installed on my machine, which is why it passed locally). All three failing jobs were that one `ModuleNotFoundError`, in the `python-test` step. I changed the test helper to stub `py4j.protocol` when the real package isn't importable. I reproduced the failure in a venv without py4j, confirmed the 7 tests pass there and with py4j installed, and that 3 of them still fail if the `fullmatch` change is reverted. Force-pushed as a single signed commit, so CI should re-run. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
