It wouldn't be very difficult to add an "ignore me please" sort of flag
on pull requests, but ignoring the ddoc only change subset of pulls
would only have a minor overall impact on tester coverage. By _far_,
the bigger issue is the number of open pull requests as a whole.
There's currently 270 open pull requests between the three repositories
(dmd, druntime, and phobos).
By design, the tester re-tests every open pull request in most recently
updated order after every merge.
If you want to help the D project, the best way to do so right now,
imho, is code reviews and getting pulls merged or closed.
On 3/4/2016 1:03 AM, BBasile via Digitalmars-d wrote:
I don't know If it's a known problem but auto tester resources are lost
by PR that only change or add DDOC comments. For example whole
dmd+runtime+phobos can be rebuild 3 times per day on 8 machines while
it's not necessary.
I understand that's a side-effect of the doc being directly in the code,
but...
Wouldn't be possible to run a background tool, based on libdparse, that
- detects changed lines in the diff.
- run the libdparse-based tool to see if changed lines are only in the
ddoc.
Depending on the results, either only CyberShadow's doc builder would
run or also the big auto-tester.
