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
Test somehow that generated files are up to date: run make regen-all #74445
Comments
bpo-23404 replaced "make touch" with "make regen-all". Generated files are no more regenerated based on file modification time anymore, the action is now explicit. Zachary Ware proposed to add a buildbot to check that generated files are up to date: run "make regen-all" and test that no file was modified. |
I also asked if something similar should be done for autoconf? |
Oh, Zachary: it seems like you already implemented this check, no? "Use Travis to make sure all generated files are up to date" |
make -j4 I understand that we build the whole Python, and only later check if generated files are up to date. Why not checking if generated files are up to date *before* compiling Python? |
#2543 confirms that the "make regen-all" test works, the CI fails with: Generated files not up to date |
#2542 confirms that the "make clinic" test works, the CI fails with: Generated files not up to date M Modules/clinic/posixmodule.c.h -- I close the issue, thanks Zach for the automated tests! |
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: