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.

Sign up for GitHub

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

Jump to bottom

no stack trace for some errors outside @test #26155

Closed
JeffBezanson opened this issue Feb 22, 2018 · 4 comments
Closed

no stack trace for some errors outside @test #26155

JeffBezanson opened this issue Feb 22, 2018 · 4 comments
Labels
error handling Handling of exceptions by Julia or the user testsystem The unit testing framework and Test stdlib

Comments

@JeffBezanson
Copy link
Member

E.g.

Error in testset FileWatching:
Error During Test at C:\cygwin\home\Administrator\buildbot\worker\package_win64\build\test\testdefs.jl:19
  Got an exception of type LoadError outside of a @test
  LoadError: FDWatcher: socket operation on non-socket (ENOTSOCK)
  in expression starting at C:\cygwin\home\Administrator\buildbot\worker\package_win64\build\usr\share\julia\site\v0.7\FileWatching\test\runtests.jl:77
ERROR: LoadError: Test run finished with errors

This makes it basically impossible to diagnose such failures.
@JeffBezanson JeffBezanson added priority This should be addressed urgently testsystem The unit testing framework and Test stdlib and removed priority This should be addressed urgently labels Feb 22, 2018
@JeffBezanson
Copy link
Member Author

OK, this does work in many cases, just not for that particular error. The error might come from a callback, which could be related.

@JeffBezanson JeffBezanson changed the title no stack trace for errors outside @test no stack trace for some errors outside @test Feb 22, 2018
@samoconnor
Copy link
Contributor

Is it related to this: #19979 (comment) ?

@JeffBezanson JeffBezanson added the error handling Handling of exceptions by Julia or the user label Feb 23, 2018
@c42f
Copy link
Member

c42f commented Oct 24, 2018

Possibly fixed by #28878 ?

@vtjnash
Copy link
Member

vtjnash commented Feb 1, 2024

Or possibly fixed by #44995, since I think @test/@testset previously used to strip out all backtrace info from the user

@vtjnash vtjnash closed this as completed Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
error handling Handling of exceptions by Julia or the user testsystem The unit testing framework and Test stdlib
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@vtjnash @c42f @JeffBezanson @samoconnor