make ccache optional #10310
Merged
make ccache optional #10310
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gnusi
approved these changes
Oct 24, 2019
fceller
added a commit
that referenced
this pull request
Oct 24, 2019
fceller
added a commit
that referenced
this pull request
Oct 24, 2019
ObiWahn
added a commit
that referenced
this pull request
Oct 24, 2019
…ture/cpp17-clean-up * 'devel' of https://github.com/arangodb/arangodb: make ccache optional (#10310) abort write transactions (#10248) url-encode and -decode in place (#10301) updated CHANGELOG upgrade boost to version 1.71.0 (#10299) Feature/explain spliced subqueries (#10298) Revert "Feature/react webpack testing (#8712)" Feature/react webpack testing (#8712) Bug fix/make result ctor noexcept (#10293) micro optimizations for case conversion (#10291) fix error message (#10281) Add Linux to -Werr (#10294) make sure error files get built when arangod is built (#10284)
ObiWahn
added a commit
that referenced
this pull request
Oct 25, 2019
…ture/switch-some-scripts-to-python3 * 'devel' of https://github.com/arangodb/arangodb: (26 commits) upgrade vpack library (#10314) avoid string copies in several cases (#10317) Round index estimates when comparing plan, we do not really care for exact equallity, they should only not be off by much (#10312) make ccache optional (#10310) abort write transactions (#10248) url-encode and -decode in place (#10301) updated CHANGELOG upgrade boost to version 1.71.0 (#10299) Feature/explain spliced subqueries (#10298) Revert "Feature/react webpack testing (#8712)" Feature/react webpack testing (#8712) Bug fix/make result ctor noexcept (#10293) micro optimizations for case conversion (#10291) fix error message (#10281) Add Linux to -Werr (#10294) make sure error files get built when arangod is built (#10284) reactivate warnings as errors (#10286) remove extra JSON parser (#10282) don't show "NaN" in web interface for cluster RAM usage (#10283) Bug fix/some future massaging (#10285) ...
ObiWahn
added a commit
that referenced
this pull request
Oct 28, 2019
…ture/smart-join-views-2 * 'devel' of https://github.com/arangodb/arangodb: rawPayload shouldn't return the full reply buffer (#10319) micro optimizations (#10316) test attempt to increase max collection name length from 64 chars to 256 (#9890) Feature/force backup (#10265) upgrade vpack library (#10314) avoid string copies in several cases (#10317) Round index estimates when comparing plan, we do not really care for exact equallity, they should only not be off by much (#10312) make ccache optional (#10310)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Guidelines
Pull requests are an essential collaborative tool for modern software development.
The below list is intended to help you figure out whether your code is ready to be reviewed
and merged into ArangoDB. The overarching goal is to:
Acceptance Checklist
The below list is not exhaustive, think thoroughly whether the provided information is sufficient.
Remove options that do not apply
Scope & Purpose
(Can you describe what functional change your PR is trying to effect?)
Related Information
(Please reference tickets / specification etc )
Testing & Verification
This change is a trivial rework / code cleanup without any test coverage.
Notes
This needs to be ported to upstream!