Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

scripts/release:release_test is failing #2003

Closed
katre opened this issue Oct 28, 2016 · 2 comments
Closed

scripts/release:release_test is failing #2003

katre opened this issue Oct 28, 2016 · 2 comments
Assignees
Labels
P2 We'll consider working on this in future. (Assignee optional) type: bug

Comments

@katre
Copy link
Member

katre commented Oct 28, 2016

Error Message

Expected 'release-v0', was 'master'
Stacktrace

Creating new release branch release-v0 for release v0
Switched to a new branch 'release-v0'
Applying cherry-picks
Creating release notes
[release-v0 2698d89] Release v0 (2016-10-28)
 Author: Bazel Release System <noreply@google.com>
 1 file changed, 7 insertions(+)
 create mode 100644 CHANGELOG.md
Created v0RC1 on branch release-v0.
-- Test log: -----------------------------------------------------------
------------------------------------------------------------------------
test_release_workflow FAILED: Expected 'release-v0', was 'master' .
/home/ci/.cache/bazel/_bazel_ci/5127b335231a9ca705b921842b9cfa0d/bazel-sandbox/efa7aa1f-4a84-42cc-9bc6-17d2dc17cd2c-76/execroot/linux-x86_64/bazel-out/local-fastbuild/bin/scripts/release/release_test.runfiles/io_bazel/scripts/release/release_test:56: in call to create
/home/ci/.cache/bazel/_bazel_ci/5127b335231a9ca705b921842b9cfa0d/bazel-sandbox/efa7aa1f-4a84-42cc-9bc6-17d2dc17cd2c-76/execroot/linux-x86_64/bazel-out/local-fastbuild/bin/scripts/release/release_test.runfiles/io_bazel/scripts/release/release_test:143: in call to test_release_workflow
@katre katre added type: bug P2 We'll consider working on this in future. (Assignee optional) labels Oct 28, 2016
@katre
Copy link
Member Author

katre commented Oct 28, 2016

Kristina, I think you updated this recently?

@kchodorow
Copy link
Contributor

Yup, that's my fault.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 We'll consider working on this in future. (Assignee optional) type: bug
Projects
None yet
Development

No branches or pull requests

2 participants