commit | ba18ee7bbc9d794f831f7625c21a566a3882382d | [log] [tgz] |
---|---|---|
author | Alex Fandrianto <alexfandrianto@google.com> | Mon Mar 21 19:32:59 2016 -0700 |
committer | Alex Fandrianto <alexfandrianto@google.com> | Mon Mar 21 19:34:05 2016 -0700 |
tree | 76ab7b2e0086f5cea37c539de7281eb1aa322ae6 | |
parent | 96795aa56a9213bcb036b8c4e6e5c3ffc3497f34 [diff] |
mojo/v23proxy: Add logs to isolate Flake area There are a few places where we wait for data to arrive, so I think it would help to add these print statements to the test. Note: The test has been flaky on Jenkins but not locally. Change-Id: Ibc81caee0ba810259d175f81713e484e7e24bb8a
This repository implements the proposal outlined here that enables communication between Mojo applications on different devices.
You must have the jiri
tool installed with the base
and mojo
v23-profiles.
To update v23proxy to the latest version of mojo, you will need to also have the mojo-dev
profile.
You must always make build
first. (The Makefile is not very good currently.)
make build
ANDROID=1 make build
The commands above build the .mojo
shared library that can be run by mojo shells. For example:
make start-v23proxy
HOME=/tmp make ARGS="{see Makefile}" start-echo-client
You can also run these with Android devices. Use an ANDROID={N}
prefix to run on the Nth
Android device connected to your machine. N
must be a positive integer.
Note: To run these examples, the devices used must run mojo_shell on the same local network.
Prefix all commands with USE_MOJO_DEV_PROFILE=1
in order to run with the mojo-dev
profile instead of mojo
.