On Oct 20, 11:14 am, Marc Guillemot <[EMAIL PROTECTED]> wrote: > Norris Boyd wrote: > > We have a big change coming with the new abstract syntax tree (AST) > > APIs getting ready to land in CVS. This change is large enough that I > > think we should first release a 1.7R2 version, then expose the AST API > > on CVS so people have more chance to use the new features and > > comment. > > > You can see the changes in 1.7R2 > > here:http://developer.mozilla.org/En/New_in_Rhino_1.7R2 > > > The 1.7R2 release candidate is available from FTP at > >ftp://ftp.mozilla.org/pub/mozilla.org/js/rhino1_7R2-RC1.zip. > > > Thanks, > > Norris > > I'm quite surprised: how can you publish a RC with a build that doesn't > run all the tests (in fact that doesn't even compile them all) and where > a not small number of tests fail (98 standard tests on my machine, and > > 10 of the ones that are not considered in build)? > > Or do you perhaps have an other way to test the quality of the code base > which is not the obvious one? In this case, can you perhaps share it, it > would be helpful to know what are the rules when submitting patches. > > Cheers, > Marc. > -- > Web:http://www.efficient-webtesting.com > Blog:http://mguillem.wordpress.com
Which tests are you referring to? I run the tests that are shared with SpiderMonkey using org.mozilla.javascript.drivers.JsDriver, which has skip lists, see http://developer.mozilla.org/En/Running_the_Rhino_tests. Those tests all pass for me, although I need to resync to pull down any new tests that have been introduced on the SpiderMonkey side. How are you running tests? Using org.mozilla.javascript.drivers.StandardTests? --N _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
