Revision: 22834
Author: [email protected]
Date: Mon Aug 4 19:17:21 2014 UTC
Log: Fix spurious debug-script assertion after enabling Symbols
This approach, of allowing either N or N+1 in this assert,
is the same approach used before my Symbols patch that naively
changed to use assertEquals.
[email protected]
Review URL: https://codereview.chromium.org/439833002
http://code.google.com/p/v8/source/detail?r=22834
Modified:
/branches/bleeding_edge/test/mjsunit/debug-script.js
=======================================
--- /branches/bleeding_edge/test/mjsunit/debug-script.js Mon Aug 4
18:17:54 2014 UTC
+++ /branches/bleeding_edge/test/mjsunit/debug-script.js Mon Aug 4
19:17:21 2014 UTC
@@ -59,7 +59,7 @@
}
// This has to be updated if the number of native scripts change.
-assertEquals(21, named_native_count);
+assertTrue(named_native_count == 20 || named_native_count == 21);
// Only the 'gc' extension is loaded.
assertEquals(1, extension_count);
// This script and mjsunit.js has been loaded. If using d8, d8 loads
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
