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

[Zoltan Somogyi]

2021-07-23 15:55 GMT+10:00 "Peter Wang" <novalazy at gmail.com>:
> On Thu, 22 Jul 2021 17:27:43 +1000 "Zoltan Somogyi" <zoltan.somogyi at runbox.com> wrote:
>> 
>> 2021-07-22 17:17 GMT+10:00 "Peter Wang" <novalazy at gmail.com>:
>> > 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).
>> 
>> It would take only a few lines in that script to implement "we have started
>> the tests now, don't print any more output".
> 
> Done.

Thanks.
 
>> > 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
>> 
>> Ah, the "locked filing cabinet in a disused lavatory, behind a beware of the leopard sign"
>> kind of available :-(
> 
> Hardly. But, I've made links to each failed test's log file now.

Thank you. I apologise for the above remark, but you have agree
that the method you described has zero discoverability.

Zoltan.