commit | b1c18614e63aeb781c75681f5ff393576dc9e8ab | [log] [tgz] |
---|---|---|
author | Robert Iannucci <iannucci@chromium.org> | Tue Jun 04 01:28:53 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Jun 04 01:28:53 2019 |
tree | 199f45d43dfac21fed350c128adae6ac81070fee | |
parent | c2b6b7ae345169e8f0a09f767467ddd897542a25 [diff] |
Fix logdog client library on windows. LOGDOG_STREAM_SERVER_PATH is set to e.g. `net.pipe:LUCILogDogKitchen_1176` on bots, but the file to open is '\\.\pipe\LUCILogDogKitchen_1176'. Additionally, specify no-buffering and '+' mode to prevent python from hanging onto bytes it shouldn't keep and allow the pipe to be re-opened for multiple streams in the same python process. R=tandrii@chromium.org Bug: 910369 Change-Id: I47948856a5ac91f87f61eeee8e56e6e093ec3a96 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1642647 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
Recipes are a domain-specific language (embedded in python) for specifying sequences of subprocess calls in a cross-platform and testable way.
They allow writing build flows which integrate with the rest of LUCI.
Documentation for the recipe engine (including this file!). Take a look at the user guide for some hints on how to get started. See the implementation details doc for more detailed implementation information about the recipe engine.
user.email
and user.name
are configured in git config
.Run the following to setup the code review tool and create your first review:
# Get `depot_tools` in $PATH if you don't have it git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git $HOME/src/depot_tools export PATH="$PATH:$HOME/src/depot_tools" # Check out the recipe engine repo git clone https://chromium.googlesource.com/infra/luci/recipes-py $HOME/src/recipes-py # make your change cd $HOME/src/recipes-py git new-branch cool_feature # hack hack git commit -a -m "This is awesome" # This will ask for your Google Account credentials. git cl upload -s -r joe@example.com # Wait for approval over email. # Click "Submit to CQ" button or ask reviewer to do it for you. # Wait for the change to be tested and landed automatically.
Use git cl help
and git cl help <cmd>
for more details.