cd languages && make test Had a LOT of failures recently. I just: - fixed up some APL that was using crufty parrot (that I myself broke but never noticed because of...) - ... TODO'd some more APL that used to work aeons ago that I don't have time to diagnose before the release - temporarily removed 5 languages from unified testing because they are failing many of their tests (lua, PIR, scheme, urm, Zcode)
There are still a few failures remaining: befunge/t/basic.t (Wstat: 256 Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 1 jako/t/examples.t (Wstat: 256 Tests: 15 Failed: 1) Failed test: 1 Non-zero exit status: 1 ook/t/basic.t (Wstat: 256 Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 1 tcl/t/cmd_lsort.t (Wstat: 256 Tests: 22 Failed: 0) Non-zero exit status: 1 tcl/t/cmd_namespace.t (Wstat: 0 Tests: 21 Failed: 0) Parse errors: Bad plan. You planned 39 tests but ran 21. The first tcl failure is a result of the inferior runloop problem. All tests pass, but the file fails. I can move the one offending test into a separate file that isn't run by the unified harness as a stopgap, if this is desired. The second tcl failure is a result of recent changes to the namespace PMC. The eventual goal of this cleanup is to get these tests running via smolder to give core developers more feedback on their commits. The aborted test in this file can be TODOd if we can't fix the root cause before release. The short term goal is to have a relatively clean languages-test for the release. -- Will "Coke" Coleda
