[erlang-questions] how: I would like to write a good bug report

Lukas Larsson <>
Tue Jun 19 16:28:46 CEST 2012


Hi,

The stacktrace below and a description of which version of Erlang you
are running should be enough for a basic bug report. If more info is
needed, we'll get back to you.

As for the error, I suspect that the SUITE has been compiled with a
pre R15B compiler and is being run with a post R15B runtime. Recomping
the SUITE with a new compiler should solve the problem.

We try to be backwards compatible in the interfaces, but it seems we
missed this scenario.

Lukas

On Tue, Jun 19, 2012 at 12:01 PM, Bengt Kleberg
<> wrote:
> Greetings,
>
> After the switch to R15B01 I get the following crash(*) when I run a
> test. How should I make a good bug report? Is is sufficient with:
> "ct_line module is missing line/1 function"
> ?
>
>
> bengt
>
> === Ended at 2012-06-19 10:36:01
> === location [{ct_line,line},
>  {sbg_st_legacy_char_SUITE,init_per_suite,0},
>  {test_server,ts_tc,1834},
>  {test_server,run_test_case_eval1,1434},
>  {test_server,run_test_case_eval,1302}]
> === reason = undefined function ct_line:line/1
>  in function  sbg_st_legacy_char_SUITE:init_per_suite/1
>  in call from test_server:ts_tc/3 (test_server.erl, line 1834)
>  in call from test_server:run_test_case_eval1/6 (test_server.erl, line
> 1434)
>  in call from test_server:run_test_case_eval/9 (test_server.erl, line
> 1302)
> ===
> *** init_per_suite failed.
>    Skipping all cases.
>
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions



More information about the erlang-questions mailing list