Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove uncaught-exception listener #127

Merged
merged 2 commits into from
Jan 15, 2015
Merged

Remove uncaught-exception listener #127

merged 2 commits into from
Jan 15, 2015

Conversation

Raynos
Copy link
Collaborator

@Raynos Raynos commented Dec 14, 2014

A testing library should not have an uncaught-exception listener, it makes testing hard code like uncaught exceptions harder.

For example
`

$ node endpoints/user/test/
TAP version 13
# can register

/home/raynos/projects/manga-feed/node_modules/tape/index.js:75
        throw err
              ^
RangeError: Maximum call stack size exceeded

Tape intercepts my range error and ruins the stack by rethrowing.

The particular PIPE bug we were gaurding against is better dealt with by adding
an error listener on process.stdout or something.

Not really sure which EPIPE we are gaurding against. I recommend removing it
for now and we can add it back later.

The previous commit removed the uncaught exception interception.
However that code was needed to get the process to write the
uncaught stack trace on failures.

Since messing with uncaught exception messes with the way we
exit the only way to know if exit is called from uncaught exception
is to monkey patch node core and keep track of the state
@Raynos
Copy link
Collaborator Author

Raynos commented Jan 5, 2015

If no one objects to this change then I will land it.

@Raynos
Copy link
Collaborator Author

Raynos commented Jan 5, 2015

cc @substack et al.

Raynos added a commit that referenced this pull request Jan 15, 2015
Remove uncaught-exception listener
@Raynos Raynos merged commit b938b8d into master Jan 15, 2015
vvo pushed a commit to defunctzombie/zuul that referenced this pull request Jul 1, 2015
+ add browser_output_timeout option, default to no timeout like before
So that cloud testing does not hangs when uncaught exception thrown
or any other funny thing
Related to (but also useful for anyone) tape-testing/tape#127 and
tape-testing/tape#134
This fixes #185
+ add browser_retries option, default to 6 like before
+ some more debugging information to ease .. debugging
ngryman pushed a commit to ngryman/zuul that referenced this pull request Jul 19, 2015
+ add browser_output_timeout option, default to no timeout like before
So that cloud testing does not hangs when uncaught exception thrown
or any other funny thing
Related to (but also useful for anyone) tape-testing/tape#127 and
tape-testing/tape#134
This fixes defunctzombie#185
+ add browser_retries option, default to 6 like before
+ some more debugging information to ease .. debugging
@ljharb ljharb deleted the remove branch March 4, 2019 00:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant