This is a work in progress evaluating script execution options to see if we can speed up the ensure-up-to-date process in the short term before any changes related to #6333 (closed)
Switched from a mix of sh, eval, and script execution to /bin/bash with stdout redirecting to /dev/null results in:
./bin/utils/ensure-up-to-date 1118.22s user 82.57s system 191% cpu 10:26.87 totalSwitched from /bin/bash to /usr/bin/env bash and installed bash 5.0, the results were similar:
./bin/utils/ensure-up-to-date 1119.88s user 82.50s system 195% cpu 10:16.37 totalPR checklist
-
Read the contribution guidelines. -
If contributing template-only or documentation-only changes which will change sample output, build the project before. -
Run the shell script(s) under ./bin/(or Windows batch scripts under.\bin\windows) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run./bin/{LANG}-petstore.sh,./bin/openapi3/{LANG}-petstore.shif updating the code or mustache templates for a language ({LANG}) (e.g. php, ruby, python, etc). -
File the PR against the correct branch: master,4.3.x,5.0.x. Default:master. -
Copy the technical committee to review the pull request if your PR is targeting a particular programming language.