"ant runtests" has failures

[GoogleCodeExporter]

"ant runtests" reports the following failures:

guest-scan-min  Failure 100000 ms passed while waiting for: completion 
(Remaining elements = [<div id="testUniverse-caja-guest-0___" 
class="testcontainer done failed">])

junit.framework.AssertionFailedError: 100000 ms passed while waiting for: 
completion (Remaining elements = [<div id="testUniverse-caja-guest-0___" 
class="testcontainer done failed">])
    at com.google.caja.plugin.BrowserTestCase.countdown(BrowserTestCase.java:262)
    at com.google.caja.plugin.BrowserTestCase.waitForCompletion(BrowserTestCase.java:222)
    at com.google.caja.plugin.BrowserTestCase.driveBrowser(BrowserTestCase.java:209)
    at com.google.caja.plugin.BrowserTestCase.runBrowserTest(BrowserTestCase.java:130)
    at com.google.caja.plugin.CatalogTestCase.runTest(CatalogTestCase.java:34)
    at com.google.caja.plugin.CatalogRunner$1.evaluate(CatalogRunner.java:94)
    at com.google.caja.plugin.CatalogRunner.runChild(CatalogRunner.java:88)
    at com.google.caja.plugin.CatalogRunner.runChild(CatalogRunner.java:42)

282.660
taming-tamed-min    Failure The title shows 1/40 fail 39/40 pass - Browser test 
case (Netscape 5.0 (Macintosh))

junit.framework.AssertionFailedError: The title shows 1/40 fail 39/40 pass - 
Browser test case (Netscape 5.0 (Macintosh))
    at com.google.caja.plugin.BrowserTestCase.driveBrowser(BrowserTestCase.java:213)
    at com.google.caja.plugin.BrowserTestCase.runBrowserTest(BrowserTestCase.java:130)
    at com.google.caja.plugin.CatalogTestCase.runTest(CatalogTestCase.java:34)
    at com.google.caja.plugin.CatalogRunner$1.evaluate(CatalogRunner.java:94)
    at com.google.caja.plugin.CatalogRunner.runChild(CatalogRunner.java:88)
    at com.google.caja.plugin.CatalogRunner.runChild(CatalogRunner.java:42)

Original issue reported on code.google.com by erights on 15 Dec 2014 at 1:38

[GoogleCodeExporter]

Original comment by kpreid@google.com on 17 Dec 2014 at 12:31

• Changed state: Started

[GoogleCodeExporter]

taming-tamed is doing a sanity check on the taming frame that assumes (as a 
self-test of the test) there is a primordial getter and setter to be found, 
which on Firefox w/ the arguments/caller changes is no longer true. Not sure 
what to do about that — suggestions?

guest-scan is complaining because it's no longer the case that you can obtain 
[[ThrowTypeError]] from function instances. I'm changing it to use a more 
direct path.

Neither of these failures indicates an underlying problem.

Original comment by kpreid@google.com on 17 Dec 2014 at 12:43

[GoogleCodeExporter]

I dealt with taming-tamed by adding a dummy accessor property just for the test.

https://codereview.appspot.com/188350043

Original comment by kpreid@google.com on 17 Dec 2014 at 10:11

• Changed state: Pending

[GoogleCodeExporter]

@r5706

Original comment by kpreid@google.com on 17 Dec 2014 at 11:06

• Changed state: Fixed