Hi, On Mon, 29 Jun 2026 at 20:17, Álvaro Herrera <[email protected]> wrote: > > A little belatedly, I've made this work and the report can be seen here: > > https://coverage.postgresql.org/diff/ > > It refreshes once a day.
Thanks for setting this up! > I'm open to suggestions for improvement. Examples just off the top of > my head: ... > - baseline is the tip of the previous stable branch. Seems odd to me. > Shouldn't it be the branch point from the current master? I think this makes sense. This is probably a better way to show 'what things have been changed in the current development cycle'. > - should we have one report per live branch, instead of just master? I think just master is okay. However, since this is generated once per-day; it doesn't hurt to have one report per live branch. > - date bins are 1, 7, 30, 360. Is that good? Looks good to me. > - What other tests can we run? Should we set PG_TESTS_EXTRA? PG_TESTS_EXTRA is already set in the script, are you asking to disable it? If so, I think it is okay to have them enabled; at least the ones which increase the coverage. > - Two tests seem to be failing, but I didn't investigate why. > (Scrollback wasn't kept by tmux; see the first point above.) I can investigate them if you want. Perhaps in the same website but something like: https://coverage.postgresql.org/out/ ? -- Regards, Nazir Bilal Yavuz Microsoft
