On 2/9/12 3:48 AM, Alvis Yardley wrote:
Hello all:
The guide states, "[a] couple of weeks in advance of the release, ask people
to run "make fulltest" and report (and hopefully fix!) any problems they
discover." So, I'm asking folks to "run 'make fulltest'" and "report (and
hopefully fix!) any problems ... [you] discover."
So I have indeed been running 'make fulltest', and in the process have
encountered errors in 6 or 7 coding standards tests. I've fixed some of
them, but these still remain:
Test Summary Report
-------------------
t/codingstd/c_arg_assert.t (Wstat: 256 Tests: 2 Failed: 1)
Failed test: 1
Non-zero exit status: 1
t/codingstd/c_function_docs.t (Wstat: 256 Tests: 236 Failed: 1)
Failed test: 86
Non-zero exit status: 1
t/codingstd/c_parens.t (Wstat: 256 Tests: 3 Failed: 1)
Failed test: 3
Non-zero exit status: 1
t/codingstd/opcode_doc.t (Wstat: 256 Tests: 1 Failed: 1)
Failed test: 1
Non-zero exit status: 1
Files=33, Tests=453, 62 wallclock secs ( 0.16 usr 0.05 sys + 59.83 cusr
1.12 csys = 61.16 CPU)
Result: FAIL
make: *** [nocritic_codetest] Error 1
These failures represent a regression from our situation as of the 4.0
release three weeks ago. So people who have added the C functions and
the (experimental) opcodes that are undocumented should create some
basic documentation for them so that the c_functions_docs.t and
opcode_doc.t tests once again PASS.
I'll try to get the other tests to PASS, but others with more C-fu than
I are welcome to give them a shot as well.
Thank you very much.
Jim Keenan
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
