Re: rebar3 as test compile not fetching test dependencies

Fred Hebert <[email protected]> Thu, 13 Jan 2022 13:46:26 -0500
Newsgroups gmane.comp.lang.erlang.general
Message-ID <CAFA3VZKvxfj0WhjNcUGFi=iVE2n-MXvwL3Q5tK1ynJ8T+W128w@mail.gmail.com>
Here's a sample run with 3.17.0, which I had already pre-installed:

λ /tmp → rebar3 new lib chk
===> Writing chk/src/chk.erl
===> Writing chk/src/chk.app.src
===> Writing chk/rebar.config
===> Writing chk/.gitignore
===> Writing chk/LICENSE
===> Writing chk/README.md
λ /tmp → cd chk
λ chk → vim rebar.config
λ chk → cat rebar.config
{profiles, [
  {test, [{deps, [gun, meck]}]}
]}.
λ chk → rebar3 as test compile
===> Verifying dependencies...
===> Fetching gun v1.3.3
===> Fetching meck v0.9.2
===> Fetching cowlib v2.7.3
===> Analyzing applications...
===> Compiling meck
===> Compiling cowlib
===> Compiling gun
_build/test/lib/gun/src/gun.erl:654:29: Warning: erlang:get_stacktrace/0 is
removed; use the new try/catch syntax for retrieving the stack backtrace

===> Analyzing applications...
===> Compiling chk

I would probably advise to double-check the configuration format (see the
sample one I have included and displayed). This is pretty core
functionality and thoroughly tested, so I'd be very surprised to see it
break.

On Thu, Jan 13, 2022 at 8:47 AM Anthony Howe <[email protected]> wrote:

> Has anyone seen this happening?
>
> Using rebar3 3.16.1, I remove the whole `_build` directory, my
> `rebar.config`
> has a `test` profile with `deps` (gun and meck) specified.  I do `rebar3
> as test
> compile` and it fetches all the default dependencies, but not the test
> ones,
> which of course means the test suites fail.
>
> I also tried rebar 3.18.0.
>
> --
> Anthony C Howe                                                 SnertSoft
> [email protected]     Twitter: SirWumpus            BarricadeMX & Milters
> http://snert.com/    http://nanozen.snert.com/     http://snertsoft.com/
>