Great!<br><br><div><span class="gmail_quote">On 2/3/07, <b class="gmail_sendername">Leonardo Santagada</b> <<a href="mailto:santagada@gmail.com">santagada@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
We are able to parse most of the mozilla suite of tests, so I made a<br>little driver (a thing that runs the mozilla suite) to run the tests<br>against our interpreter. Most of the tests suite breaks after the<br>parsing on some missing opcode or when trying to access some non
<br>implemented function (or object, or prototype, or constructor). The<br>parts that get as far as finishing building the test cases are here:<br><br>6-2.js passed 5 of 5 tests<br>7.1-1.js passed 4 of 4 tests<br>7.1-2.js
passed 3 of 3 tests<br>7.7.2.js passed 1 of 1 tests<br>7.7.3-1.js passed 25 of 25 tests<br>7.7.3.js passed 166 of 184 tests<br>10.1.3.js passed 15 of 15 tests<br>10.1.6.js passed 0 of 16 tests<br>10.2.3-1.js passed 0 of 2 tests
<br>11.12-1.js passed 6 of 6 tests<br>11.13.2-2.js passed 2 of 58 tests<br>11.13.2-3.js passed 2 of 76 tests<br>11.13.2-4.js passed 14 of 36 tests<br>11.13.2-5.js passed 6 of 44 tests<br>11.13.js passed 6 of 6 tests<br>11.14-1.js
passed 2 of 2 tests<br>11.2.2-11.js passed 1 of 1 tests<br>11.5.1.js passed 26 of 26 tests<br>11.6.3.js passed 20 of 24 tests<br>11.9.1.js passed 29 of 63 tests<br>11.9.2.js passed 29 of 63 tests<br>11.9.3.js passed 29 of 63 tests
<br>12.5-1.js passed 3 of 7 tests<br>12.5-2.js passed 3 of 7 tests<br>15.1.1.1.js passed 2 of 2 tests<br>15.1.1.2.js passed 2 of 2 tests<br>15.2.2.2.js passed 2 of 2 tests<br>15.3.5.1.js passed 0 of 2 tests<br>15.4.1.3.js
passed 1 of 5 tests<br>15.4.2.2-2.js passed 0 of 14 tests<br>15.6.1.js passed 19 of 19 tests<br>15.6.3.1-4.js passed 0 of 2 tests<br>15.6.3.js passed 0 of 2 tests<br>15.6.4.2-1.js passed 0 of 46 tests<br>15.7.3.1-2.js passed 0 of 2 tests
<br>15.8-1.js passed 0 of 2 tests<br><br>Not much but this is just the start. If someone wants to run all<br>tests on their machines just checkout the latest revision and run<br>driver.py... it will try to run all the test suite (yep, i'm planning
<br>on improving this) and write the results to result.txt while on<br>screen you get what tests are running. Warning: this might take some<br>hours<br><br>Somehow my code crashed the python interpreter (2.4.4) on one of the
<br>test files... will try to reproduce the crash and send a bug report<br>upstream.<br><br>Now I will work on some simple stuff like the MOD operator and this<br>kind of stuff to make more tests run :)<br><br>abraços,<br>
Leonardo Santagada<br><br><br>_______________________________________________<br><a href="mailto:pypy-dev@codespeak.net">pypy-dev@codespeak.net</a><br><a href="http://codespeak.net/mailman/listinfo/pypy-dev">http://codespeak.net/mailman/listinfo/pypy-dev
</a><br></blockquote></div><br><br clear="all"><br>-- <br><a href="http://www.goldwatches.com">http://www.goldwatches.com</a><br><a href="http://www.wazoozle.com">http://www.wazoozle.com</a>