-
Notifications
You must be signed in to change notification settings - Fork 66
[ML] build boost test framework in buildenv #157
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
[ML] build boost test framework in buildenv #157
Conversation
droberts195
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are also two instances of --without-test in build-setup/windows.md that need removing.
|
👍 changed it locally but forgot to save/push it. done now. |
droberts195
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Relates elastic#156 This change includes changes similar to those made in elastic#157, but for the 6.x branch, and also incorporates rebuilds of VM setup bundles and Docker image updates.
Relates elastic#156 This is basically the other half of elastic#157. It does the things that were done for the 6.x branch in elastic#263 that weren't done in elastic#157. One extra point of confusion is that the macOS Docker image does not need updating in this PR because it was already rebuilt by elastic#225 using the updated instructions of elastic#157. So elastic#225 added Boost Test for macOS for the master branch.
Relates #156 This is basically the other half of #157. It does the things that were done for the 6.x branch in #263 that weren't done in #157. One extra point of confusion is that the macOS Docker image does not need updating in this PR because it was already rebuilt by #225 using the updated instructions of #157. So #225 added Boost Test for macOS for the master branch.
enable build of boost test framework in all provision steps and change documentation accordingly
Relates to #156