-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slow compilation of projects with yrl files on rebar 3.7.0-rc2 #1937
Comments
Interesting. I'm guessing this might be related to the new compiler structure @tsloughter added. One interesting thing is that I guess they are possibly missing some checks for a changed target, which would prompt for the re-compiling? |
@ferd yea, pretty sure it is likely a screw up with the digraph in the compile changes. Looking today. |
err, nevermind, looks like yrl files were never in the digraph. Must just be the check against the time the erl file was created. Will find it. |
I've got a fix and should have a PR soon. It turns out we actually have a test for this.. so I'm now trying to figure out why the test didn't catch it. I'm not happy with the fix, I want to make it more generic, but it may be good enough to merge for now. |
This makes no sense. The test checks if the beam file's last modifies time stamp changes. Which it should if the erl file's last modified time stamp changes. I added into the test a check on the erl file changing and it does indeed then fail. But have to figure out why that isn't causing the beam file to change... |
D'oh. Got it. Wasn't looking up the beam file on the right path! Which then last_modified just returns 0 both times and Ok, have a shitty fix PR coming in a minute. |
Hi! Since moving to 3.7.0-rc2 my project has taken longer to compile.
I think that the yrl file is failing to be cached so that rebar3 is generating the erl file for the yrl file every time, even when the yrl file does not change, though I do not know how to confirm this.
Here are the details:
Here is the yrl file I'm compiling.
The text was updated successfully, but these errors were encountered: