{"action":"created","issue":{"url":"https://api.github.com/repos/bazelbuild/bazel/issues/6657","repository_url":"https://api.github.com/repos/bazelbuild/bazel","labels_url":"https://api.github.com/repos/bazelbuild/bazel/issues/6657/labels{/name}","comments_url":"https://api.github.com/repos/bazelbuild/bazel/issues/6657/comments","events_url":"https://api.github.com/repos/bazelbuild/bazel/issues/6657/events","html_url":"https://github.com/bazelbuild/bazel/pull/6657","id":379728153,"node_id":"MDExOlB1bGxSZXF1ZXN0MjMwMDk3MzA5","number":6657,"title":"Describe known issue when in-mem state is lost when running bazel builds inside docker containers e.g. in CI","user":{"login":"jakubbujny","id":5843754,"node_id":"MDQ6VXNlcjU4NDM3NTQ=","avatar_url":"https://avatars3.githubusercontent.com/u/5843754?v=4","gravatar_id":"","url":"https://api.github.com/users/jakubbujny","html_url":"https://github.com/jakubbujny","followers_url":"https://api.github.com/users/jakubbujny/followers","following_url":"https://api.github.com/users/jakubbujny/following{/other_user}","gists_url":"https://api.github.com/users/jakubbujny/gists{/gist_id}","starred_url":"https://api.github.com/users/jakubbujny/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jakubbujny/subscriptions","organizations_url":"https://api.github.com/users/jakubbujny/orgs","repos_url":"https://api.github.com/users/jakubbujny/repos","events_url":"https://api.github.com/users/jakubbujny/events{/privacy}","received_events_url":"https://api.github.com/users/jakubbujny/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-11-12T11:10:01Z","updated_at":"2018-11-12T11:10:06Z","closed_at":null,"author_association":"NONE","pull_request":{"url":"https://api.github.com/repos/bazelbuild/bazel/pulls/6657","html_url":"https://github.com/bazelbuild/bazel/pull/6657","diff_url":"https://github.com/bazelbuild/bazel/pull/6657.diff","patch_url":"https://github.com/bazelbuild/bazel/pull/6657.patch"},"body":"I hit that problem and discovered answer by reading that doc: https://docs.bazel.build/versions/master/user-manual.html#flag--batch \r\n\r\nI was trying to understand why my jobs on CI takes around 20s even with caching but in dockers when locally it was like 200 ms. So maybe it would be better to place it in docs for future generations.\r\n"},"comment":{"url":"https://api.github.com/repos/bazelbuild/bazel/issues/comments/437842021","html_url":"https://github.com/bazelbuild/bazel/pull/6657#issuecomment-437842021","issue_url":"https://api.github.com/repos/bazelbuild/bazel/issues/6657","id":437842021,"node_id":"MDEyOklzc3VlQ29tbWVudDQzNzg0MjAyMQ==","user":{"login":"googlebot","id":5384588,"node_id":"MDQ6VXNlcjUzODQ1ODg=","avatar_url":"https://avatars3.githubusercontent.com/u/5384588?v=4","gravatar_id":"","url":"https://api.github.com/users/googlebot","html_url":"https://github.com/googlebot","followers_url":"https://api.github.com/users/googlebot/followers","following_url":"https://api.github.com/users/googlebot/following{/other_user}","gists_url":"https://api.github.com/users/googlebot/gists{/gist_id}","starred_url":"https://api.github.com/users/googlebot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/googlebot/subscriptions","organizations_url":"https://api.github.com/users/googlebot/orgs","repos_url":"https://api.github.com/users/googlebot/repos","events_url":"https://api.github.com/users/googlebot/events{/privacy}","received_events_url":"https://api.github.com/users/googlebot/received_events","type":"User","site_admin":false},"created_at":"2018-11-12T11:10:06Z","updated_at":"2018-11-12T11:10:06Z","author_association":"NONE","body":"\nThanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).\n\n:memo: **Please visit <https://cla.developers.google.com/> to sign.**\n\nOnce you've signed (or fixed any issues), please reply here (e.g. `I signed it!`) and we'll verify it.\n\n----\n\n#### What to do if you already signed the CLA\n\n##### Individual signers\n\n*   It's possible we don't have your GitHub username or you're using a different email address on your commit. Check [your existing CLA data](https://cla.developers.google.com/clas) and verify that your [email is set on your git commits](https://help.github.com/articles/setting-your-email-in-git/).\n\n##### Corporate signers\n\n*   Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to [go/cla#troubleshoot](http://go/cla#troubleshoot) ([Public version](https://opensource.google.com/docs/cla/#troubleshoot)).\n*   The email used to register you as an authorized contributor must be the email used for the Git commit. Check [your existing CLA data](https://cla.developers.google.com/clas) and verify that your [email is set on your git commits](https://help.github.com/articles/setting-your-email-in-git/).\n*   The email used to register you as an authorized contributor must also be [attached to your GitHub account](https://github.com/settings/emails).\n\t\t\n\n<!-- need_sender_cla -->"}}
{"actor":{"display_login":"googlebot"}}