imbajin opened a new pull request, #507: URL: https://github.com/apache/hugegraph-doc/pull/507
## Change Site CI spends much more time validating rendered output than running Hugo. This first experiment reuses already parsed canonical metadata and target lookups, and validates version artifacts with at most two processes on the existing aggregate runner. Every version, security, route and browser check remains enabled; output assembly stays serial and only starts after all version validations succeed. Before: validate each version serially, repeatedly parse the same page and validate the same route map. After: reuse immutable validation inputs and perform bounded parallel validation, with explicit stage timings. ## Validation - Python 3.13 source tests and workflow contracts passed locally. - Fresh latest strict build and validation passed with Hugo 0.165 Extended. - Added actual process failure-propagation and serial/parallel output-equivalence tests. - Independent review found no blocker in the validator/aggregate changes. ## Performance experiment Baseline: [master run 36998587106](https://github.com/apache/hugegraph-doc/actions/runs/36998587106), commit `3e8d3e33a4e98dd9d2f713ba9ed8ac1fc15ccc7a`. | Metric | Baseline | PR | | --- | ---: | ---: | | Prepare start to required gate | 603 s | Pending | | Run creation to required gate (includes initial wait) | 683 s | Pending | | Required jobs, summed runner time | 974 s | Pending | | Aggregate assembly and validation | 185 s | Pending | | Browser and JS tests | 132 s | Pending | This is a draft while CI measurements are collected. The next controlled experiment will compare historical artifact reuse and fewer build jobs, including cold and warm caches. Keep changes only when the end-to-end results justify them; do not trade away validation coverage for an isolated step improvement. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
