Runtime tests failing on interpreter branch

[tcr]

This is a tracking bug for colony-interpreter merge.

Currently these tests fail with tinytap on runtime-qemu. They may be false negatives (but not false positives) due to

• Poor UART handling in Qemu
• Not packaging in tinytap (yet)
• Tinytap missing tests that are, in fact, invalid
• HTTP disabled

➜  why git:(master) ✗ tinytap -e "../../run.js ../../out/Release/main.bin {}" suite/*.js
1..52
ok 1 - suite/__proto__.js
ok 2 - suite/arguments.js
ok 3 - suite/array.js
ok 4 - suite/bind.js
not ok 5 - suite/bitmath.js
not ok 6 - suite/buffer.js
not ok 7 - suite/bug-bindnull.js
not ok 8 - suite/bug-endwithcomments.js
not ok 9 - suite/bug-foreach-null.js
not ok 10 - suite/bug-forinarray.js
not ok 11 - suite/bug-regexreplace.js
ok 12 - suite/bug-underscores.js
not ok 13 - suite/builtin.js
ok 14 - suite/console.js
not ok 15 - suite/crypto.js
not ok 16 - suite/date.js
ok 17 - suite/defineProperty.js
not ok 18 - suite/delete.js
not ok 19 - suite/early-return.js
not ok 20 - suite/encoding.js
ok 21 - suite/error.js
ok 22 - suite/etters.js
ok 23 - suite/event-error.js
ok 24 - suite/fs-streams.js
ok 25 - suite/fs.js
ok 26 - suite/function.js
ok 27 - suite/hasOwnProperty.js
not ok 28 - suite/hash.js
not ok 29 - suite/http.js
not ok 30 - suite/https.js
ok 31 - suite/json.js
ok 32 - suite/jsonload.js
ok 33 - suite/keywords.js
not ok 34 - suite/math.js
not ok 35 - suite/net.js
ok 36 - suite/number.js
ok 37 - suite/parse-numbers.js
ok 38 - suite/primitive.js
ok 39 - suite/process.js
ok 40 - suite/regex.js
not ok 41 - suite/streams.js
not ok 42 - suite/string-decoder.js
ok 43 - suite/string.js
ok 44 - suite/timers.js
not ok 45 - suite/tls.js
not ok 46 - suite/truthy.js
not ok 47 - suite/try.js
not ok 48 - suite/unicode.js
not ok 49 - suite/url.js
not ok 50 - suite/util.js
ok 51 - suite/with.js
not ok 52 - suite/zlib.js
not ok 53 - (not all tests pass.)
➜  why git:(master) ✗ tinytap -e "../../run.js ../../out/Release/main.bin {}" issues/*.js
1..126
ok 1 - issues/issue-beta-100.js
ok 2 - issues/issue-beta-101.js
ok 3 - issues/issue-beta-108.js
ok 4 - issues/issue-beta-131.js
ok 5 - issues/issue-beta-140.js
ok 6 - issues/issue-beta-148.js
not ok 7 - issues/issue-beta-159.js
not ok 8 - issues/issue-beta-162.js
ok 9 - issues/issue-beta-170.js
ok 10 - issues/issue-beta-179.js
ok 11 - issues/issue-beta-180.js
not ok 12 - issues/issue-beta-180b.js
ok 13 - issues/issue-beta-195.js
ok 14 - issues/issue-beta-200.js
ok 15 - issues/issue-beta-204.js
not ok 16 - issues/issue-beta-207.js
ok 17 - issues/issue-beta-212.js
ok 18 - issues/issue-beta-213.js
ok 19 - issues/issue-beta-221.js
not ok 20 - issues/issue-beta-242.js
ok 21 - issues/issue-beta-243.js
not ok 22 - issues/issue-beta-244.js
ok 23 - issues/issue-beta-245.js
ok 24 - issues/issue-beta-251.js
ok 25 - issues/issue-beta-274.js
ok 26 - issues/issue-beta-276.js
ok 27 - issues/issue-beta-294.js
ok 28 - issues/issue-beta-296.js
ok 29 - issues/issue-beta-314.js
ok 30 - issues/issue-beta-317.js
ok 31 - issues/issue-beta-319.js
ok 32 - issues/issue-beta-327.js
ok 33 - issues/issue-beta-334.js
not ok 34 - issues/issue-beta-337.js
ok 35 - issues/issue-beta-338.js
ok 36 - issues/issue-beta-339.js
not ok 37 - issues/issue-beta-340.js
ok 38 - issues/issue-beta-342.js
ok 39 - issues/issue-beta-351.js
ok 40 - issues/issue-beta-352.js
ok 41 - issues/issue-beta-356.js
not ok 42 - issues/issue-beta-366.js
ok 43 - issues/issue-beta-379.js
ok 44 - issues/issue-beta-380.js
ok 45 - issues/issue-beta-390.js
ok 46 - issues/issue-beta-394.js
ok 47 - issues/issue-beta-395.js
ok 48 - issues/issue-beta-402.js
ok 49 - issues/issue-beta-440.js
ok 50 - issues/issue-beta-446.js
not ok 51 - issues/issue-beta-451.js
not ok 52 - issues/issue-beta-73.js
ok 53 - issues/issue-beta-77.js
ok 54 - issues/issue-beta-81.js
ok 55 - issues/issue-beta-84.js
ok 56 - issues/issue-beta-87.js
ok 57 - issues/issue-beta-93.js
ok 58 - issues/issue-beta-97.js
ok 59 - issues/issue-beta-98.js
not ok 60 - issues/issue-runtime-107.js
ok 61 - issues/issue-runtime-109.js
ok 62 - issues/issue-runtime-117.js
ok 63 - issues/issue-runtime-122.js
ok 64 - issues/issue-runtime-133.js
ok 65 - issues/issue-runtime-146.js
ok 66 - issues/issue-runtime-150.js
ok 67 - issues/issue-runtime-156.js
ok 68 - issues/issue-runtime-158.js
ok 69 - issues/issue-runtime-159.js
ok 70 - issues/issue-runtime-170.js
ok 71 - issues/issue-runtime-173.js
ok 72 - issues/issue-runtime-177.js
not ok 73 - issues/issue-runtime-185.js
ok 74 - issues/issue-runtime-186.js
ok 75 - issues/issue-runtime-190.js
ok 76 - issues/issue-runtime-191.js
ok 77 - issues/issue-runtime-199.js
ok 78 - issues/issue-runtime-204.js
ok 79 - issues/issue-runtime-208.js
ok 80 - issues/issue-runtime-223.js
ok 81 - issues/issue-runtime-234.js
ok 82 - issues/issue-runtime-239.js
ok 83 - issues/issue-runtime-244.js
ok 84 - issues/issue-runtime-246.js
ok 85 - issues/issue-runtime-269.js
ok 86 - issues/issue-runtime-276.js
not ok 87 - issues/issue-runtime-282.js
ok 88 - issues/issue-runtime-283.js
ok 89 - issues/issue-runtime-287.js
ok 90 - issues/issue-runtime-289.js
ok 91 - issues/issue-runtime-292.js
ok 92 - issues/issue-runtime-295.js
ok 93 - issues/issue-runtime-296.js
ok 94 - issues/issue-runtime-297.js
ok 95 - issues/issue-runtime-298.js
ok 96 - issues/issue-runtime-302.js
ok 97 - issues/issue-runtime-303.js
ok 98 - issues/issue-runtime-304.js
ok 99 - issues/issue-runtime-305.js
not ok 100 - issues/issue-runtime-306.js
ok 101 - issues/issue-runtime-307.js
not ok 102 - issues/issue-runtime-314.js
ok 103 - issues/issue-runtime-320.js
ok 104 - issues/issue-runtime-337.js
ok 105 - issues/issue-runtime-345.js
not ok 106 - issues/issue-runtime-360.js
ok 107 - issues/issue-runtime-362.js
ok 108 - issues/issue-runtime-368.js
ok 109 - issues/issue-runtime-373.js
ok 110 - issues/issue-runtime-385.js
not ok 111 - issues/issue-runtime-388.js
ok 112 - issues/issue-runtime-397.js
ok 113 - issues/issue-runtime-419.js
ok 114 - issues/issue-runtime-420.js
ok 115 - issues/issue-runtime-434.js
ok 116 - issues/issue-runtime-437.js
ok 117 - issues/issue-runtime-448.js
not ok 118 - issues/issue-runtime-450.js
ok 119 - issues/issue-runtime-472.js
ok 120 - issues/issue-runtime-473.js
ok 121 - issues/issue-runtime-491.js
not ok 122 - issues/issue-runtime-492.js
ok 123 - issues/issue-runtime-506.js
ok 124 - issues/issue-runtime-524.js
ok 125 - issues/issue-runtime-529.js
not ok 126 - issues/log-global.js
not ok 127 - (not all tests pass.)

[tcr]

Of the miscellaneous failures, the ones considered blockers are:

• [x] suite/bitmath.js
• [x] suite/buffer.js
• [x] suite/date.js
• [x] suite/truthy.js
• [x] issues/issue-runtime-282.js
• [x] issues/issue-runtime-306.js
• [x] issues/issue-runtime-314.js

[tcr]

After breezing through those, we now have a different subset of failures:

• [x] issues/issue-beta-334.js
• [x] issues/issue-runtime-173.js
• [x] issues/issue-runtime-297.js
• [x] issues/issue-runtime-320.js
• [x] issues/issue-runtime-472.js
• [x] suite/bitmath.js
• [x] suite/buffer.js
• [x] suite/encoding.js

And more after "event-error".

[tcr]

Tests are now passing, and this is kicked off to the two following problems:

• [ ] runtime-qemu has intermittent failures due to UART handling
• [ ] runtime tests need to be ported to tinytap, not old-style tap handling (many tests have no TAP output, incorrect, etc.)

[tcr]

And we're good!