[erlang-bugs] R16 EUnit *** context setup failed ***
Thu Jan 31 16:51:33 CET 2013
Thanks for bisecting!
I will fix the bug in R16B.
On Thu, Jan 31, 2013 at 1:11 AM, Tuncer Ayaz <> wrote:
> On Fri, Nov 23, 2012 at 4:20 PM, Anthony Ramine wrote:
> > I can reproduce this with the exact same steps.
> This is the git-bisect result:
> 70b5e24c9498225fadc08d19503269c8aad851bf is the first bad commit
> commit 70b5e24c9498225fadc08d19503269c8aad851bf
> Author: Bjorn Gustavsson <>
> Date: Tue Sep 11 15:03:53 2012 +0200
> Fix filelib:wildcard/2
> filelib:wildcard("some/relative/path/*.beam", Path) would fail to
> match any file. That is, filelib:wildcard/2 would not work if the
> first component of the pattern did not contain any wildcard
> Noticed-by: Samuel Rivas
> > Le 13 nov. 2012 à 14:18, Tuncer Ayaz a écrit :
> >> If I build and run rebar's EUnit tests with R16, I see "*** context
> >> setup failed ***" errors.
> >> Interestingly, if I use a tree where ebin/*, rebar, and .eunit/*.beam
> >> have been built with R15B02, then neither R16 nor R15 throw the
> >> context setup errors.
> >> # fetch and build rebar
> >> $ git clone git://github.com/rebar/rebar.git
> >> $ cd rebar
> >> $ make
> >> # run tests with new rebar binary
> >> $ ./rebar eunit
> >> # *** context setup failed *** errors and 50 out of 72 tests
> >> # not executed
> >> $ rm ebin/* .eunit/* rebar
> >> # rebuild rebar and EUnit tests with R15
> >> $ make && ./rebar eunit
> >> # running EUnit tests with either R15 or R16 works now
> >> Can anyone else reproduce this? Could this be caused by compiler
> >> changes in R16? I don't see any changes in lib/eunit after R15B02.
Björn Gustavsson, Erlang/OTP, Ericsson AB
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-bugs