[M3devel] www.opencm3.net/m3tests

[Olaf Wagner]

Quoting Jay <jayk123 at hotmail.com>:

> The "problem" here, a really really small one, is just that the link  
>  and mt commands got echoed.
> Olaf made them not echoed. I then made them conditionally echoed.
>   I made m3-sys\m3tests define M3TESTS so that NT386.common doesn't echo.
> It's not a big deal either way.
> Aha -- tests in other directories would have a problem, and I think   
> there are some.
>
> I like more echoing usually, so the system explains what is going on,
> instead of the vaguer "linking foo" sort of message.
> Granted, nobody bothers watching gcc run assembler commands, so I   
> guess it is just quite gray.

Jay, cm3 needs to behave the same on all platforms. By default
commands should _not_ be echoed to stdout or stderr; that's what the
-commands switch is for: this gives you exactly the commands the
compiler issues to invoke other tools.

For more verbose output, you may also depend on the -verbose or the
-debug switches.

Please adapt the configuration files that bey default all echoing
of commands is off.

Olaf

> I don't know how to run the Tinderbox either yet, sorry.
> I tried.
>
> For adding tests, well, there is m3-sys\m3tests.
> That is where a lot of the tests are, but not all.
> I am not sure where tests belong. I added a small number there.
> They are named with just a letter and a number.
> The letters have some meaning, explained in the m3makefile.
> "p" is programs that are run and their stdout/stderr compared   
> against expected
> "e" is programs build and the errors from the compiler checked to be  
>  reasonable.
>   I don't think in general they are expected to successfully compile  
>  or run, though the case of "warnings" may be unclear.
> "c" is programs built so a human can look at the generated code.
> There is another case I think for human checking.
> The numbers are just 001, 002, 003, etc.
> Each hundred tests are in a separate directory, like p0\p001,   
> p0\p002, p1\p100, p1\101, etc.
>
> Something like this.
> Wherever I have details wrong, just look in m3-sys\m3tests. It's   
> pretty simple, obvious, and well commented.
>
> The output is a little clearer if you have a working diff.exe on the path.
> Then what you do is search for "@@" in the output.
>
>  - Jay
>
>
> Date: Tue, 6 May 2008 03:46:27 +0200From: dabenavidesd at yahoo.esTo:   
> m3devel at elegosoft.comSubject: [M3devel] www.opencm3.net/m3testsDear   
> developers:Does the recent tests on NT386 seem broken because a   
> recent change on the m3-sys tree, or is the HTML bad generated, I   
> mean can you check the last tests Sunday, May 4th (p001 to p042) has  
>  a red background   
> http://www.opencm3.net/m3tests/m3tests-NT386-2008-04-23-13-30-57.html</pre></td></tr> <tr class="bgred tl"><td> p002 </td><td class="small" width="45%"> Text</td><td class="small"><pre>Comparing files P0\P002\stdout.build and ..\SRC\P0\P002\STDOUT.BUILD***** P0\P002\stdout.buildlink @_m3responsefile0.txt 2>&1 > pgm.lstmt /nologo /manifest pgm.exe.manifest /outputresource:pgm.exe;1***** ..\SRC\P0\P002\STDOUT.BUILD*****Comparing files P0\P002\stderr.build and ..\SRC\P0\P002\STDERR.BUILDFC: no differences encounteredComparing files P0\P002\stdout.pgm and ..\SRC\P0\P002\STDOUT.PGMFC: no differences encounteredComparing files P0\P002\stderr.pgm and ..\SRC\P0\P002\STDERR.PGMFC: no differences encounteredand almost the same pattern in the above tests.I would suggest if it is thinkable using NT386 variant with a complete dedicated machine/system, I can try to set up one this week and send the data back (the machine is behind a proxy), but I don't remember the mail explaining the set up, and also want to know if there is a chance of run the tests with one run script.Also what is the best natural way to put a new tests, and the standard name it should   
> have?Thanks
>
>
> Enviado desde Correo Yahoo!La bandeja de entrada más inteligente.



-- 
Olaf Wagner -- elego Software Solutions GmbH
                Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
phone: +49 30 23 45 86 96  mobile: +49 177 2345 869  fax: +49 30 23 45 86 95
    http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194