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
Allow stderr of executed cmake python code appear in logs #3398
Conversation
Signed-off-by: Enrico Minack <github@enrico.minack.dev>
There was a related PR #3203, which also wanted to change logging levels, but I didn't really understand why. |
Unit Test Results 801 files ± 0 801 suites ±0 9h 45m 57s ⏱️ + 28m 9s Results for commit c66b7bd. ± Comparison against base commit 19040e9. This pull request removes 8 tests.
This pull request skips 4 tests.
♻️ This comment has been updated with latest results. |
Unit Test Results (with flaky tests) 895 files - 94 895 suites - 94 10h 26m 7s ⏱️ - 1h 17m 20s For more details on these failures, see this check. Results for commit c66b7bd. ± Comparison against base commit 19040e9. This pull request removes 8 tests.
This pull request skips 4 tests.
♻️ This comment has been updated with latest results. |
I like your proposed outline to handle stderr content. I would like to see that in all places, not just one one framework. Lets leave that for #3203 and have |
@maxhgerlach any idea why some of the tests may have disappeared (not even skipped)? |
Looks like the HEAD failures did not make it into the test results. But this would also mean that these tests only run against HEAD versions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, there were numerous problems with tf-nightly
over the last few days. I looked into them for a bit because at first there appeared to be linker failures related to the changes I introduced with #3128, but those disappeared with a newer nightly build. Seems to be somewhat in turmoil.
I don't know off hand which tests would only be run on head versions.
CMake executes Python code to detect installed frameworks. If that code fails, there is no trace in the logs, which makes identifying the cause very difficult. We only see it could not find the framework:
This allows errors from the Python code to leak into the build log: