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

investigate how to get a backtrace on warnings #10

Closed
thomas-neitmann opened this issue Apr 7, 2021 · 1 comment
Closed

investigate how to get a backtrace on warnings #10

thomas-neitmann opened this issue Apr 7, 2021 · 1 comment

Comments

@thomas-neitmann
Copy link
Contributor

No description provided.

@thomas-neitmann
Copy link
Contributor Author

This is not possible. The only option is to turn warnings into error using options(warn = 2) and then running traceback() once the error occurs.

jimrothstein added a commit that referenced this issue Dec 12, 2024
@jimrothstein
2521 - typo in Test #10 for derive_var_trtemfl
e975ef4
bundfussr added a commit that referenced this issue Dec 20, 2024
@jimrothstein @bundfussr
Closes #2581 - enhance test coverage: derive_var_trtemfl.R (#2608)
982faf8 
* 2581 - enhance test coverage: derive_var_trtemfl.R

* 2581 fix styler error

* 2521 - typo in Test #10 for derive_var_trtemfl

* # 2581 Test #9, fix typo

* 2581 derive_var_trtemfl() - correct Test 11 to use `expect_snapshot` so exact error msg is caught

---------

Co-authored-by: Stefan Bundfuss <80953585+bundfussr@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@thomas-neitmann