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
Some CIs silence potentially useful output from make #83880
Comments
I think the Github action for building CPython on Ubuntu is accidentally caching the built Python files. If we take a look at: https://github.com/python/cpython/runs/455936632#step:7:1 It seems like it's running way too fast (and producing too little output) to actually be building all of CPython. Adding Steve who originally authored the action to the nosy list to see if they might have any insight. |
46s seems okay to me, especially since the 23s for autoconf is separate. Try introducing a warning/error into the source code and see if it breaks. |
Aah sorry. This was my mistake, I didn't notice that we're passing Steve, is there a reason the Github action and Azure pipelines:
both pass
|
Probably just where I copied it from. PRs welcome! |
Had to disable the doctests in the 3.7 branch because I just couldn't get them passing. Pablo did the work for 3.8 and later though, so they're on for those. |
The text "TEST CHANGE TO BE UNDONE" is currently visible here: https://docs.python.org/3/whatsnew/3.0.html It was introduced in commit 343bc06. Should this test change have been undone? |
Opened up a quick pull request to fix it: #21089 |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: