Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure in test_generate_micro_mutable_op_resolver_tests.sh script #2739

Open
AdrianLundell opened this issue Oct 30, 2024 · 4 comments
Open
Assignees
Labels

Comments

@AdrianLundell
Copy link
Contributor

The version of setuptools pinned in #2733 is incompatible with bazel, more info here: pypa/setuptools#4487. Manually downgrading to 70.3.0 resolves this issue.

Tested on commit 389e775, using bazel 7.2.1 on a x86 machine

> tensorflow/lite/micro/tools/ci_build/test_generate_micro_mutable_op_resolver_tests.sh
...

FileNotFoundError: [Errno 2] No such file or directory: '/home/matlun01/.cache/bazel/_bazel_matlun01/efbc9c212fc395edf602ea0bb1bc77d0/execroot/tflite_micro/bazel-out/k8-fastbuild/bin/tensorflow/lite/micro/tools/gen_micro_mutable_op_resolver/generate_micro_mutable_op_resolver_from_model_test.runfiles/tflm_pip_deps_setuptools/site-packages/setuptools/_vendor/jaraco/text/Lorem ipsum.txt'
@AdrianLundell
Copy link
Contributor Author

AdrianLundell commented Oct 30, 2024

Alternative fix is creating the file in the pip package installation, something like this:

export JARACO_TEXT=$(find ~/.cache -wholename "**/bin/tensorflow/lite/micro/tools/gen_micro_mutable_op_resolver/generate_micro_mutable_op_resolver_from_model_test.runfiles/tflm_pip_deps_setuptools/site-packages/setuptools/_vendor/jaraco/text")  #Or wherever else the error message points
touch $JARACO_TEXT/Lorem ipsum.txt"

Copy link
Contributor

"This issue is being marked as stale due to inactivity. Remove label or comment to prevent closure in 5 days."

@github-actions github-actions bot added the Stale label Nov 27, 2024
Copy link
Contributor

github-actions bot commented Dec 2, 2024

"This issue is being closed because it has been marked as
stale for 5 days with no further activity."

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 2, 2024
@mansnils mansnils reopened this Dec 2, 2024
@github-actions github-actions bot removed the Stale label Dec 3, 2024
Copy link
Contributor

"This issue is being marked as stale due to inactivity. Remove label or comment to prevent closure in 5 days."

@github-actions github-actions bot added the Stale label Dec 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants