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

Error: {badrecord,state_t} #66

Closed
oubiwann opened this issue Oct 13, 2020 · 1 comment
Closed

Error: {badrecord,state_t} #66

oubiwann opened this issue Oct 13, 2020 · 1 comment
Milestone

Comments

@oubiwann
Copy link
Member

An issue I am seeing in the updated, LFE 2.0-dev branch, is that even though a project's tests may pass, I still see an error at the end of the test report printout:

===> Uncaught error in rebar_core. Run with DEBUG=1 to see stacktrace or consult rebar3.crashdump
===> Uncaught error: {badrecord,state_t}

and the sole contents of the rebar3.crashdump file are:

Error: {badrecord,state_t}
[]

The state_t reference if from rebar3, in https://github.com/erlang/rebar3/blob/master/src/rebar_state.erl.

I need to dig into the final steps of the ltest plugin (reporting, summing stats, etc.), and see where that might be coming from.

@oubiwann
Copy link
Member Author

oubiwann commented Oct 13, 2020

Fixed! Culprit was a redundant {ok ...} being returned in the rebar3_lfe plugin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant