rebar3 3.7.0-rc2 build erlydtl failed.

no-trace-of-time commented 6 years ago

Pre-Check

If you are filing for a bug, please do a quick search in current issues first
For bugs, mention if you are willing or interested in helping fix the issue
For questions or support, it helps to include context around your project or problem
Think of a descriptive title (more descriptive than 'feature X is broken' unless it is fully broken)

Environment

rebar3 3.7.0-rc2 erlydtl master/0.12.1

Add the result of rebar3 report to your message: --------------------ERROR MSG ------------------------- [simonxu@centos7 erlydtl]$ !DE DEBUG=1 rebar3 eunit ===> Evaluating config script "rebar.config.script" ===> Expanded command sequence to be run: [{default,app_discovery}, {default,install_deps}, {default,lock}, {default,eunit}] ===> Provider: {default,app_discovery} ===> Evaluating config script "/projects/projects/gitee/pg/pg_web/_build/default/plugins/erlydtl/src/erlydtl.app.src.script" ===> Provider: {default,install_deps} ===> Verifying dependencies... ===> Provider: {default,lock} ===> Provider: {default,eunit} ===> run_hooks("/projects/projects/gitee/pg/pg_web/_build/default/plugins/erlydtl", pre_hooks, compile) -> no hooks defined

===> Compiling erlydtl ===> run_hooks("/projects/projects/gitee/pg/pg_web/_build/default/plugins/erlydtl", pre_hooks, compile) -> no hooks defined

===> run_hooks("/projects/projects/gitee/pg/pg_web/_build/default/plugins/erlydtl", pre_hooks, erlc_compile) -> no hooks defined

/projects/projects/gitee/pg/pg_web/_build/default/plugins/erlydtl/src/include/erlydtl_preparser.hrl: no such file or directory ===> Compiling src/erlydtl_parser.yrl failed /projects/projects/gitee/pg/pg_web/_build/default/plugins/erlydtl/src/include/erlydtl_preparser.hrl:none: no such file or directory

===> Compilation failed: {error, [["/projects/projects/gitee/pg/pg_web/_build/default/plugins/erlydtl/src/include/erlydtl_preparser.hrl:no ne: no such file or directory\n"]], []}

After I switch back to rebar3 3.6.2, erlydtl compiles without any error.

$ rebar3 report "my failing command"
...

Verify whether the version of rebar3 you're running is the latest release (see https://github.com/erlang/rebar3/releases)
If possible, include information about your project and its structure. Open source projects or examples are always easier to debug. If you can provide an example code base to reproduce the issue on, we will generally be able to provide more help, and faster.

Current behaviour

Describe the current behaviour. In case of a failure, crash, or exception, please include the result of running the command with debug information:

DEBUG=1 rebar3 <my failing command>

Expected behaviour

Describe what you expected to happen.

tsloughter commented 6 years ago

Can you try #1952 to see if this fixes your issue?

ferd commented 5 years ago

No further report since november following a potential fix being merged; will consider this resolved and someone can reopen if it still happens.

erlang / rebar3