Giters

lfex / ltest

A Testing Framework for LFE (successor to lfeunit)

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Error: {badrecord,state_t}

oubiwann opened this issue · comments

commented

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.

commented

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