Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / grpc-grpc / 21e7dfc71269e9dcb4b9b5423e3c99c2bb0d16d7
commit21e7dfc71269e9dcb4b9b5423e3c99c2bb0d16d7[log] [tgz]
authorNathaniel Manista <nathaniel@google.com>Sun Mar 12 18:24:09 2017 +0000
committerNathaniel Manista <nathaniel@google.com>Sun Mar 12 18:24:09 2017 +0000
treee49e2afc34b909e14d8318354444135834700406
parent0b7bd20de4f0d219c399ef8c01c05026bf12da5d [diff]
Ignore the number of failed skipped tests

jobset.run was changed on 16 October 2015 in e4c3561074ca27fc4bdf1a6bf
to return the number of failures and the result set. On 20 October 2016
in 5c691c634de144b50fc1f2e166303219721c19d0 jobset.run was changed to
allow jobs to be skipped, but the introduced code path only returned
the result set, giving jobset.run inconsistent return value semantics.
On 24 October 2016 7e9bd6ca9a2e167dcb6133c78c05cf27584ee062 introduced
a use of jobset.run's "skip_jobs" return value semantics, and on 8
March 2017 d159af31fcf300cfe2d7b9b41d789cd664ee4f1b resolved
jobset.run's inconsistent return value semantics but failed to correct
run_tests_matrix's use of the inconsistent "skip_jobs" return value
semantics.
1 file changed
tree: e49e2afc34b909e14d8318354444135834700406
  1. bazel/
  2. cmake/
  3. doc/
  4. etc/
  5. examples/
  6. include/
  7. src/
  8. summerofcode/
  9. templates/
  10. test/
  11. third_party/
  12. tools/
  13. vsprojects/
  14. .clang-format
  15. .clang_complete
  16. .editorconfig
  17. .gitignore
  18. .gitmodules
  19. .istanbul.yml
  20. .pylintrc
  21. .rspec
  22. .travis.yml
  23. .yardopts
  24. binding.gyp
  25. BUILD
  26. build.yaml
  27. build_config.rb
  28. CMakeLists.txt
  29. composer.json
  30. config.m4
  31. CONTRIBUTING.md
  32. Gemfile
  33. gRPC-Core.podspec
  34. gRPC-ProtoRPC.podspec
  35. gRPC-RxLibrary.podspec
  36. grpc.bzl
  37. grpc.def
  38. grpc.gemspec
  39. gRPC.podspec
  40. INSTALL.md
  41. LICENSE
  42. Makefile
  43. MANIFEST.md
  44. package.json
  45. package.xml
  46. PATENTS
  47. PYTHON-MANIFEST.in
  48. Rakefile
  49. README.md
  50. requirements.txt
  51. setup.cfg
  52. setup.py
  53. WORKSPACE
README.md

Build Status

gRPC - An RPC library and framework

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

Copyright 2015 Google Inc.

#Documentation

You can find more detailed documentation and examples in the doc and examples directories respectively.

#Installation & Testing

See INSTALL for installation instructions for various platforms.

See tools/run_tests for more guidance on how to run various test suites (e.g. unit tests, interop tests, benchmarks)

See Performance dashboard for the performance numbers for v1.0.x.

#Repository Structure & Status

This repository contains source code for gRPC libraries for multiple languages written on top of shared C core library [src/core] (src/core).

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

LanguageSourceStatus
Shared C [core library][src/core] (src/core)1.0
C++[src/cpp] (src/cpp)1.0
Ruby[src/ruby] (src/ruby)1.0
NodeJS[src/node] (src/node)1.0
Python[src/python] (src/python)1.0
PHP[src/php] (src/php)1.0
C#[src/csharp] (src/csharp)1.0
Objective-C[src/objective-c] (src/objective-c)1.0

See MANIFEST.md for a listing of top-level items in the repository.

#Overview

Remote Procedure Calls (RPCs) provide a useful abstraction for building distributed applications and services. The libraries in this repository provide a concrete implementation of the gRPC protocol, layered over HTTP/2. These libraries enable communication between clients and servers using any combination of the supported languages.

##Interface

Developers using gRPC typically start with the description of an RPC service (a collection of methods), and generate client and server side interfaces which they use on the client-side and implement on the server side.

By default, gRPC uses Protocol Buffers as the Interface Definition Language (IDL) for describing both the service interface and the structure of the payload messages. It is possible to use other alternatives if desired.

###Surface API Starting from an interface definition in a .proto file, gRPC provides Protocol Compiler plugins that generate Client- and Server-side APIs. gRPC users typically call into these APIs on the Client side and implement the corresponding API on the server side.

Synchronous vs. asynchronous

Synchronous RPC calls, that block until a response arrives from the server, are the closest approximation to the abstraction of a procedure call that RPC aspires to.

On the other hand, networks are inherently asynchronous and in many scenarios, it is desirable to have the ability to start RPCs without blocking the current thread.

The gRPC programming surface in most languages comes in both synchronous and asynchronous flavors.

Streaming

gRPC supports streaming semantics, where either the client or the server (or both) send a stream of messages on a single RPC call. The most general case is Bidirectional Streaming where a single gRPC call establishes a stream where both the client and the server can send a stream of messages to each other. The streamed messages are delivered in the order they were sent.

#Protocol

The gRPC protocol specifies the abstract requirements for communication between clients and servers. A concrete embedding over HTTP/2 completes the picture by fleshing out the details of each of the required operations.

Abstract gRPC protocol

A gRPC RPC comprises of a bidirectional stream of messages, initiated by the client. In the client-to-server direction, this stream begins with a mandatory Call Header, followed by optional Initial-Metadata, followed by zero or more Payload Messages. The server-to-client direction contains an optional Initial-Metadata, followed by zero or more Payload Messages terminated with a mandatory Status and optional Status-Metadata (a.k.a.,Trailing-Metadata).

Implementation over HTTP/2

The abstract protocol defined above is implemented over HTTP/2. gRPC bidirectional streams are mapped to HTTP/2 streams. The contents of Call Header and Initial Metadata are sent as HTTP/2 headers and subject to HPACK compression. Payload Messages are serialized into a byte stream of length prefixed gRPC frames which are then fragmented into HTTP/2 frames at the sender and reassembled at the receiver. Status and Trailing-Metadata are sent as HTTP/2 trailing headers (a.k.a., trailers).

Flow Control

gRPC inherits the flow control mechanisms in HTTP/2 and uses them to enable fine-grained control of the amount of memory used for buffering in-flight messages.