You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This run, while properly running the unittests in the proper modules, will generate a faulty dependency file that only contain standard library and druntime stuff.
The same happens when using a module instead an --eval, in which case, only the dependency of that module are tracked properly, and the dependencies of the modules added via --extra-file remain untracked.
This is a major issue as it leads rdmd to reuse cache entries when it shouldn't and run outdated code.
Comments
The text was updated successfully, but these errors were encountered:
deadalnix reported this on 2021-09-02T22:08:52Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=22268
CC List
Description
$ rdmd -m64 -Isrc -w -debug -g -unittest -i --extra-file=src/module1.d --extra-file=src/module2.d --eval="/* Do nothing */"
This run, while properly running the unittests in the proper modules, will generate a faulty dependency file that only contain standard library and druntime stuff.
The same happens when using a module instead an --eval, in which case, only the dependency of that module are tracked properly, and the dependencies of the modules added via --extra-file remain untracked.
This is a major issue as it leads rdmd to reuse cache entries when it shouldn't and run outdated code.
Comments
The text was updated successfully, but these errors were encountered: