make test-debugger fails hard, amirite? #3156
Labels
test
Issues and PRs related to the tests.
Comments
|
Same on Fedora 22 (8 fails / 10) |
|
I've wasted a disproportionate amount of time on them over the years and won't be sad to seem them go, FWIW. |
|
For what it's worth, it appears that we now have it down to 6 of 10 tests failing. Progress, I guess. |
Trott
added a commit
to Trott/io.js
that referenced
this issue
Mar 2, 2016
`test-debug-break-on-uncaught` was hanging on the domain and parse error scenarios. These tests are not run in CI and may have been broken for a very long time. Refs: nodejs#3156 Refs: nodejs@c16963b9
jasnell
pushed a commit
that referenced
this issue
Mar 7, 2016
`test-debug-break-on-uncaught` was hanging on the domain and parse error scenarios. These tests are not run in CI and may have been broken for a very long time. Refs: #3156 Refs: c16963b9 PR-URL: #5532 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rod Vagg <r@va.gg>
Fishrock123
pushed a commit
that referenced
this issue
Mar 8, 2016
`test-debug-break-on-uncaught` was hanging on the domain and parse error scenarios. These tests are not run in CI and may have been broken for a very long time. Refs: #3156 Refs: c16963b9 PR-URL: #5532 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rod Vagg <r@va.gg>
Fishrock123
pushed a commit
that referenced
this issue
Mar 8, 2016
`test-debug-break-on-uncaught` was hanging on the domain and parse error scenarios. These tests are not run in CI and may have been broken for a very long time. Refs: #3156 Refs: c16963b9 PR-URL: #5532 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rod Vagg <r@va.gg>
MylesBorins
pushed a commit
that referenced
this issue
Mar 17, 2016
`test-debug-break-on-uncaught` was hanging on the domain and parse error scenarios. These tests are not run in CI and may have been broken for a very long time. Refs: #3156 Refs: c16963b9 PR-URL: #5532 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rod Vagg <r@va.gg>
MylesBorins
pushed a commit
that referenced
this issue
Mar 21, 2016
`test-debug-break-on-uncaught` was hanging on the domain and parse error scenarios. These tests are not run in CI and may have been broken for a very long time. Refs: #3156 Refs: c16963b9 PR-URL: #5532 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rod Vagg <r@va.gg>
MylesBorins
pushed a commit
that referenced
this issue
Mar 21, 2016
`test-debug-break-on-uncaught` was hanging on the domain and parse error scenarios. These tests are not run in CI and may have been broken for a very long time. Refs: #3156 Refs: c16963b9 PR-URL: #5532 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rod Vagg <r@va.gg>
|
Debugger is going to be removed in the foreseeable future. These tests are unlikely to be repaired. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
make test-debuggerresults in 8 out of 10 tests failing (current master branch on OS X 10.10.5). This isn't just me, is it? And if not, are these tests worth salvaging or should they be removed?The text was updated successfully, but these errors were encountered: