Google Git
Sign in
chromium / external / github.com / grpc / grpc.git / HEAD
commit36725b8b7e933a17d6a61bf3e1d92f8dbe6d11da[log] [tgz]
authorSergii Tkachenko <sergiitk@google.com>Fri Sep 05 18:06:39 2025
committerCopybara-Service <copybara-worker@google.com>Fri Sep 05 18:09:45 2025
tree633c8feadff01de1d50a39123550ad0e4acf66ea
parentadc886d4020500f5b73ac581bd4a4844683e2f5e [diff]
[CI] Log extra disk info for debugging BAD KOKORO WORKER WARNING (#40567)

While the tmpfs mount issue itself has been fixed (ref cl/802939093), let's make it easier for ourselves if this happens again in the future.

This change logs extra debugging disk info that will help us to solve the `BAD KOKORO WORKER WARNING` mount issue.
Additionally, I printed out some basic info about the kokoro worker, similar to what [we're already doing for macos](https://github.com/grpc/grpc/blob/a840365a0973a878735c6de66d099f040797b351/tools/internal_ci/helper_scripts/prepare_build_macos_rc#L17-L24).

Closes #40567

COPYBARA_INTEGRATE_REVIEW=https://github.com/grpc/grpc/pull/40567 from sergiitk:fix/build/py/arm-disk-space e16db5ea450f67b5490bf514076dcc0e1b290af1
PiperOrigin-RevId: 803530238
2 files changed
tree: 633c8feadff01de1d50a39123550ad0e4acf66ea
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. bazel/
  5. cmake/
  6. doc/
  7. etc/
  8. examples/
  9. include/
  10. spm-core-include/
  11. spm-cpp-include/
  12. src/
  13. summerofcode/
  14. templates/
  15. test/
  16. third_party/
  17. tools/
  18. .bazelignore
  19. .bazelrc
  20. .bazelversion
  21. .clang-format
  22. .clang-tidy
  23. .dockerignore
  24. .editorconfig
  25. .git-blame-ignore-revs
  26. .gitallowed
  27. .gitattributes
  28. .gitignore
  29. .gitmodules
  30. .istanbul.yml
  31. .pylintrc
  32. .pylintrc-examples
  33. .pylintrc-tests
  34. .rspec
  35. .yapfignore
  36. .yardopts
  37. _metadata.py
  38. AUTHORS
  39. BoringSSL-Package.swift
  40. BUILD
  41. build_autogenerated.yaml
  42. build_config.rb
  43. build_handwritten.yaml
  44. BUILDING.md
  45. CMakeLists.txt
  46. CODE-OF-CONDUCT.md
  47. composer.json
  48. CONCEPTS.md
  49. config.m4
  50. config.w32
  51. CONTRIBUTING.md
  52. CONTRIBUTING_STEPS.md
  53. Gemfile
  54. GEMINI.md
  55. GOVERNANCE.md
  56. gRPC-C++.podspec
  57. gRPC-Core.podspec
  58. gRPC-ProtoRPC.podspec
  59. gRPC-RxLibrary.podspec
  60. grpc-style-config.toml
  61. grpc.bzl
  62. grpc.def
  63. grpc.gemspec
  64. gRPC.podspec
  65. LICENSE
  66. MAINTAINERS.md
  67. Makefile
  68. MANIFEST.md
  69. MODULE.bazel
  70. NOTICE.txt
  71. Package.swift
  72. package.xml
  73. PYTHON-MANIFEST.in
  74. Rakefile
  75. README.md
  76. requirements.bazel.lock
  77. requirements.bazel.txt
  78. requirements.txt
  79. ruff.toml
  80. SECURITY.md
  81. setup.cfg
  82. setup.py
  83. TROUBLESHOOTING.md
  84. WORKSPACE
README.md

gRPC – An RPC library and framework

gRPC is a modern, open source, high-performance remote procedure call (RPC) framework that can run anywhere. gRPC enables client and server applications to communicate transparently, and simplifies the building of connected systems.

Join the chat at https://gitter.im/grpc/grpc

To start using gRPC

To maximize usability, gRPC supports the standard method for adding dependencies to a user‘s chosen language (if there is one). In most languages, the gRPC runtime comes as a package available in a user’s language package manager.

For instructions on how to use the language-specific gRPC runtime for a project, please refer to these documents

  • C++: follow the instructions under the src/cpp directory
  • C#/.NET: NuGet packages Grpc.Net.Client, Grpc.AspNetCore.Server
  • Dart: pub package grpc
  • Go: go get google.golang.org/grpc
  • Java: Use JARs from Maven Central Repository
  • Kotlin: Use JARs from Maven Central Repository
  • Node: npm install @grpc/grpc-js
  • Objective-C: Add gRPC-ProtoRPC dependency to podspec
  • PHP: pecl install grpc
  • Python: pip install grpcio
  • Ruby: gem install grpc
  • WebJS: follow the grpc-web instructions

Per-language quickstart guides and tutorials can be found in the documentation section on the grpc.io website. Code examples are available in the examples directory.

Precompiled bleeding-edge package builds of gRPC master branch's HEAD are uploaded daily to packages.grpc.io.

To start developing gRPC

Contributions are welcome!

Please read How to contribute which will guide you through the entire workflow of how to build the source code, how to run the tests, and how to contribute changes to the gRPC codebase. The “How to contribute” document also contains info on how the contribution process works and contains best practices for creating contributions.

Troubleshooting

Sometimes things go wrong. Please check out the Troubleshooting guide if you are experiencing issues with gRPC.

Performance

See the Performance dashboard for performance numbers of master branch daily builds.

Concepts

See gRPC Concepts

About This Repository

This repository contains source code for gRPC libraries implemented in multiple languages written on top of a shared C++ core library src/core.

Libraries in different languages may be in various states of development. We are seeking contributions for all of these libraries:

LanguageSource
Shared C++ [core library]src/core
C++src/cpp
Rubysrc/ruby
Pythonsrc/python
PHPsrc/php
C# (core library based)src/csharp
Objective-Csrc/objective-c
LanguageSource repo
Javagrpc-java
Kotlingrpc-kotlin
Gogrpc-go
NodeJSgrpc-node
WebJSgrpc-web
Dartgrpc-dart
.NET (pure C# impl.)grpc-dotnet
Swiftgrpc-swift