On Monday, 10 September 2018 at 01:27:20 UTC, Neia Neutuladh
wrote:
On Wednesday, 5 September 2018 at 05:44:38 UTC, H. S. Teoh
wrote:
To me, this strongly suggests the following idea:
- add *all* dlang.org packages to our current autotester / CI
infrastructure.
- if a particular (version of a) package builds successfully,
log the
compiler version / git hash / package version to a database
and add
a note to dlang.org that this package built successfully
with this
compiler version.
Not on dlang.org anywhere, but I built a crude version of this.
Results are available at http://ikeran.org/report/.
The current backfill is taking the three most recent versions
of each package on the ~40 most recent versions of dmd, using a
list of dub packages from a couple days ago. Each compiler
version takes about six hours, so the backfill will be finished
in about ten days. The report should update automatically every
100 builds.
Once that's done, I'll extend the backfill to handle all
package versions, have it get new package versions from dub,
and get it to discover and download new DMD versions
automatically. This shouldn't be a huge change.
Nice work. I wonder about some of your results, as it says that
dub itself doesn't build with all of the dmd versions, but
somehow the tests pass sometimes (shouldn't be possible if you
can't build dub itself). I just tested with `dub fetch dub; dub
build dub` with the dub 1.10 that comes alongside dmd 2.081.1 on
linux/x64 and it built the latest dub 1.11 without a problem.
Regardless, you should talk to Sonke about getting this
integrated with code.dlang.org and to Mike about putting up a
funding target to pay for both permanent server resources and
your time coding this up. I've already said I'd donate towards
such a target:
https://forum.dlang.org/post/[email protected]
