| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 年前 | ||
Remove ray.data code from global doctest conftest (#51334) Moves data-specific functionality out of the global default fixtures that are installed for doctest builds. The way this was currently implemented basically hard-coded the global conftest.py file. I had to rework this to be installed as a pytest "plugin" using the -p argument instead. The doctest build now allows overriding the plugin file. --------- Signed-off-by: Edward Oakes <ed.nmi.oakes@gmail.com> | 1 年前 | |
[core] Rename external build file (#50642) Best practice for naming external BUILD file is xxx.BUILD, otherwise vscode and plugin doesn't recognize it. I follow what well-known projects do: - grpc: https://github.com/grpc/grpc/tree/master/third_party - tensorflow: https://github.com/tensorflow/tensorflow/tree/master/third_party Signed-off-by: dentiny <dentinyhao@gmail.com> | 1 年前 | |
Remove ray.data code from global doctest conftest (#51334) Moves data-specific functionality out of the global default fixtures that are installed for doctest builds. The way this was currently implemented basically hard-coded the global conftest.py file. I had to rework this to be installed as a pytest "plugin" using the -p argument instead. The doctest build now allows overriding the plugin file. --------- Signed-off-by: Edward Oakes <ed.nmi.oakes@gmail.com> | 1 年前 | |
[core] Rename external build file (#50642) Best practice for naming external BUILD file is xxx.BUILD, otherwise vscode and plugin doesn't recognize it. I follow what well-known projects do: - grpc: https://github.com/grpc/grpc/tree/master/third_party - tensorflow: https://github.com/tensorflow/tensorflow/tree/master/third_party Signed-off-by: dentiny <dentinyhao@gmail.com> | 1 年前 | |
[core] Rename external build file (#50642) Best practice for naming external BUILD file is xxx.BUILD, otherwise vscode and plugin doesn't recognize it. I follow what well-known projects do: - grpc: https://github.com/grpc/grpc/tree/master/third_party - tensorflow: https://github.com/tensorflow/tensorflow/tree/master/third_party Signed-off-by: dentiny <dentinyhao@gmail.com> | 1 年前 | |
[core] Fix variable shadow java (#51786) Signed-off-by: dentiny <dentinyhao@gmail.com> | 1 年前 | |
[core] Rename external build file (#50642) Best practice for naming external BUILD file is xxx.BUILD, otherwise vscode and plugin doesn't recognize it. I follow what well-known projects do: - grpc: https://github.com/grpc/grpc/tree/master/third_party - tensorflow: https://github.com/tensorflow/tensorflow/tree/master/third_party Signed-off-by: dentiny <dentinyhao@gmail.com> | 1 年前 | |
[CI] Migrate from sphinx.ext.doctest to pytest-sphinx (#35286) This PR switches our doctest tooling from sphinx.ext.doctest to pytest-sphinx. Context We want to test all code snippets in CI. testcode and doctest examples are tested in CI with sphinx.ext.doctest. But, we often write code-block:: python examples, and they aren't tested in CI. Problem sphinx.ext.doctest doesn't let you test specific files. As a result, it's hard to update examples or isolate GPU examples. Solution Migrate to pytest-sphinx. Two reasons: Lets us run GPU doctests Enables developers to quickly test their examples --------- Signed-off-by: Balaji Veeramani <balaji@anyscale.com> | 3 年前 | |
Remove ray.data code from global doctest conftest (#51334) Moves data-specific functionality out of the global default fixtures that are installed for doctest builds. The way this was currently implemented basically hard-coded the global conftest.py file. I had to rework this to be installed as a pytest "plugin" using the -p argument instead. The doctest build now allows overriding the plugin file. --------- Signed-off-by: Edward Oakes <ed.nmi.oakes@gmail.com> | 1 年前 | |
[core] Rename external build file (#50642) Best practice for naming external BUILD file is xxx.BUILD, otherwise vscode and plugin doesn't recognize it. I follow what well-known projects do: - grpc: https://github.com/grpc/grpc/tree/master/third_party - tensorflow: https://github.com/tensorflow/tensorflow/tree/master/third_party Signed-off-by: dentiny <dentinyhao@gmail.com> | 1 年前 | |
| 1 年前 | ||
Revert "Revert "Revert "Revert "[core] Support encrypted redis connection." (#28991)""" (#29109) Reverts #29078 There are two issues: tsan fail and mac build fail. For TSAN, if we build redis + openssl with tsan the redis will segfault. So we exclude the redis target from the tsan build. For mac failure, the root cause is that in the CI somehow the toolchain picked in rules_foreign_cc is wrong. Failed to find any useful solution within a day. So just use the old build for mac and pick in the runtime. Since redis is only used for testing, win/mac/linux both support rediss. | 3 年前 | |
[Test] 调整测试用例，适应测试流水线 Co-authored-by: liuxianghai1<liuxianghai1@huawei.com> | 11 个月前 | |
[core] Rename external build file (#50642) Best practice for naming external BUILD file is xxx.BUILD, otherwise vscode and plugin doesn't recognize it. I follow what well-known projects do: - grpc: https://github.com/grpc/grpc/tree/master/third_party - tensorflow: https://github.com/tensorflow/tensorflow/tree/master/third_party Signed-off-by: dentiny <dentinyhao@gmail.com> | 1 年前 | |
[core] Rename external build file (#50642) Best practice for naming external BUILD file is xxx.BUILD, otherwise vscode and plugin doesn't recognize it. I follow what well-known projects do: - grpc: https://github.com/grpc/grpc/tree/master/third_party - tensorflow: https://github.com/tensorflow/tensorflow/tree/master/third_party Signed-off-by: dentiny <dentinyhao@gmail.com> | 1 年前 | |
[ci] add workspace status script (#54398) and use it to reject '@' character in HOME and USER Signed-off-by: Lonnie Liu <lonnie@anyscale.com> | 1 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 3 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 3 年前 | ||
| 11 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 |