-
Notifications
You must be signed in to change notification settings - Fork 113
Revert "Better AST value for nodes." #477
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
Conversation
|
I agree to revert this change but only after testing that the reverted code is working fine (and CodeCompass can compile themselves). |
… out of disk space when parsing CodeCompass and we do not really need it.
For me CodeCompass can parse itself with this modification reverted. |
Wait.. what... HOW?! |
On second check we do not have 24GB free space, because that only applies to the I will try out the |
493a1d6 to
97ae8bd
Compare
Only install required Boost components. Extend Xenial and Bionic PostgreSQL build with postgresql server install. Build and install CodeCompass in $HOME instead of $TRAVIS_BUILD_DIR, so the build and install directories won't be parsed on the self-parse test. Run CodeCompass self-parse test on number of available CPU cores. Replace the relative include path of Functions.cmake in webgui/InstallGUI.cmake with an absolute, so it works when the build directory is not in the source directory.
dd601a3 to
3478644
Compare
|
With the |
#425 resulted in critical error for the parser component, as CodeCompass cannot even parse itself (see #471).
Implementing USR (#429) instead of mangled names will probably fix this issue (as it eliminates the erroneous
getMangledName()method completely), but that PR also fails for segmentation fault currently.As the master branch contains such a serious issue for several weeks now and the immediate solution cannot be seen yet, I suggest to revert #425, as it introduced the bug in the first place.