-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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 doctest CI (in a full source build) because it can't find python3 during mbedtls tests #45745
Comments
It looks like the test requires python3. if(NOT MBEDTLS_PYTHON_EXECUTABLE)
message(FATAL_ERROR "Cannot build test suites without Python 3")
endif()
So just don't build test:
|
The build dependencies in full source build were broken because of LBT. That is fixed in #45746 |
I was told this runs on buildkite now, but it hasn’t gotten turned off yet here. Been broken for awhile though |
Not sure which commit fixed it, but now doctest can be built successfully. |
The doctest was not broken per se- it was only an issue in the full source build. |
@DilumAluthge Do you know if this is still an issue? |
The issue here is about the Cross-ref JuliaCI/julia-buildkite#190 |
So we should probably keep this issue open until JuliaCI/julia-buildkite#190 is fixed, and then we can double-check that this issue is fixed. |
Having doctests fail in a special build seems very far from being a release blocker. |
I believe this was on regular CI that tests is the full source build works, not something special I was doing. But it runs separately I think, once a day or something. |
After the Sparse stdlibs bump PR was merged into master, the doctest CI failed because it seems to be running certain steps that don't otherwise seem to run in other PRs. It seems to need python3.
https://build.julialang.org/#/builders/54/builds/6896/steps/12/logs/stdio
The operation being performed is
full-source-dist
and it seems to have issues with Makefile dependencies as well:@DilumAluthge @staticfloat May either of you know what is up?
The text was updated successfully, but these errors were encountered: