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

[Zoltan Somogyi]

2021-07-22 14:43 GMT+10:00 "Peter Wang" <novalazy at gmail.com>:
>> Then how did the .int files get generated ok for Julien and me
>> during a workspace bootcheck?
> 
> I don't know. That is a mystery best investigated on your respective
> machines.

Ok, I will look into that.

> To be clear, you mean that this would no longer be supported:
> 
>     mmc --intermod-opt prog.m
> 
> unless you first run:
> 
>     mmc --make-int prog.m
> 
> I'm not objecting to it, just clarifying.

That is correct.
 
> 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".

> I will add the underlines to the hyperlinks.

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.

It should not be too hard to

- get bootcheck to output the name of all unexpectedly failed test cases
  to a file,

- and then have another script go through these files

  - computing the SHA-1 of the .log file,
  - copying the .log file to (say) oldfailedtestcases/<sha1valueoftestcaselogfile>
 - outputing "FAILED TEST ...." with a hyperlink to the new file

This would avoid any potential "dangling hyperlink to .log file" problem.

Zoltan.