[m-rev.] for post-commit review: a start on getting type repn info from .int files

[Peter Wang]

On Thu, 22 Jul 2021 16:53:23 +1000 "Zoltan Somogyi" <zoltan.somogyi at runbox.com> wrote:

> > The architecture and grade names are hyperlinks. From there you can get
> > at the individual log files, e.g.
> > 
> > http://testing.mercurylang.org/builds/rotd-2021-07-21/x86_64/
> > http://testing.mercurylang.org/builds/rotd-2021-07-21/x86_64/hlc.gc/
> 
> We are talking past each other, because "log file" means two different things.
> You mean "the whole output of a run of bootcheck". I mean "the .log file of a single,
> individual failed test case".

Both are available.

> Thanks, that may help some people, but that is not what I was, and am, asking for.
> I am asking that, given a line such as
> 
> FAILED TEST invalid/abstract_solver_type-nodepend in grade hlc.gc
> 
> some part of the line should be a hyperlink to (a copy of)
> tests/invalid/abstract_solver_type.log. That would be *far* more
> useful than error message fragments such as
> 
> any_passed_as_ground.m:029:   mode error: arguments `V_10, Xs' have the
> 
> which are not intelligible in themselves.

The error message fragments are to catch warnings/errors from anywhere
in the build process, usually the C compiler. That it also displays
Mercury compiler error messages from failed tests is not really
intended, and could probably be improved (it's just a dumb awk script).

The FAILED TEST lines tells you the name of the failed test case.
You can click on the the grade name, then find the log file
for that individual test case, e.g.
http://testing.mercurylang.org/builds/rotd-2021-07-21/x86_64/hlc.gc/any_passed_as_ground-nodepend.log

Most of the time there will only be a few failed tests per grade,
so it won't be hard to find.

Peter