Remove tests expecting >64-bit ints

[kevmoo]

Fixes dart-lang/tools#1007

[sigmundch]

/cc @jmesserly - possibly Jenny has more insights into this, but I thought these tests were purposely covering >64 bit because it is technically a valid part of the html spec.

My guess is that rather than deleting the tests, we should mark them as failing, or create a new bug entry with the 2 tests so coverage can be added again in the future (likely by changing int.parse with BigInt.parse or something similar.)

[kevmoo]

Zero disagreement here. I was optimizing for moving fast. Happy to review any such change. :-)

…

On Fri, Jan 26, 2018 at 12:52 PM, sigmundch ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In test/data/tokenizer/test4.test <#65 (comment)>: > @@ -152,14 +152,6 @@ "input":"&#4294967361;", "output":["ParseError", ["Character", "\uFFFD"]]}, -{"description":"65-bit hex numeric entity", - @jmesserly <https://github.com/jmesserly> - possibly Jenny has more insights into this, but I thought these tests were purposely covering >64 bit because it is technically a valid part of the html spec. My guess is that rather than deleting the tests, we should mark them as failing, or create a new bug entry with the 2 tests so coverage can be added again in the future (likely by changing int.parse with BigInt.parse or something similar.) — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#65 (review)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABCiuKW1P5ON8oo5QKJNEwU6jNGTNVUks5tOjsAgaJpZM4RlPYx> .