Skip to content

[doc] Update developer docs with bazel instructions #4944

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.

Sign up for GitHub

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

Merged
pcmoritz merged 2 commits into from
Jun 7, 2019
Merged

[doc] Update developer docs with bazel instructions #4944

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
35732a9
Update doc
stephanie-wang Jun 6, 2019
08817dd
fix ref
pcmoritz Jun 6, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 13 additions & 2 deletions doc/source/development.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,8 +29,11 @@ recompile much more quickly by doing

.. code-block:: shell

cd ray/build
make -j8
cd ray
bazel build //:ray_pkg

This command is not enough to recompile all C++ unit tests. To do so, see
`Testing locally`_.

Debugging
---------
Expand Down Expand Up @@ -144,6 +147,14 @@ When running tests, usually only the first test failure matters. A single
test failure often triggers the failure of subsequent tests in the same
script.

To compile and run all C++ tests, you can run:

.. code-block:: shell

cd ray
bazel test $(bazel query 'kind(cc_test, ...)')


Linting
-------

Expand Down