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

CI, bazel-watcher: failing with bazel 0.9.0 rc2 #4249

Closed
laszlocsomor opened this issue Dec 7, 2017 · 6 comments
Closed

CI, bazel-watcher: failing with bazel 0.9.0 rc2 #4249

laszlocsomor opened this issue Dec 7, 2017 · 6 comments
Assignees
Labels
breakage P1 I'll work on this now. (Assignee required)

Comments

@laszlocsomor
Copy link
Contributor

Blocking: #3773

Log: https://ci.bazel.io/job/Global/job/bazel-watcher/311/console

Ran as part of Bazel 0.9.0 rc2 test: https://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/bazel/job/release/533/Downstream_projects/

Binaries: https://releases.bazel.build/0.9.0/rc2/index.html

Example log:

[node=darwin-x86_64] ERROR: /Users/ci/workspace/Global/bazel-watcher-node=darwin-x86_64/WORKSPACE:69:1: Cannot redefine repository after any load statement in the WORKSPACE file (for repository 'com_github_golang_protobuf')
[node=darwin-x86_64] ERROR: Error evaluating WORKSPACE file
[node=darwin-x86_64] ERROR: error loading package 'external': Package 'external' contains errors
[node=darwin-x86_64] INFO: Elapsed time: 0.961s
[node=darwin-x86_64] FAILED: Build did NOT complete successfully (0 packages loaded)
[node=darwin-x86_64] FAILED: Build did NOT complete successfully (0 packages loaded)
@laszlocsomor laszlocsomor added breakage P1 I'll work on this now. (Assignee required) Release blocker labels Dec 7, 2017
@laszlocsomor
Copy link
Contributor Author

TODO:

@buchgr
Copy link
Contributor

buchgr commented Dec 8, 2017

I can confirm that it works with 0.8.1 and fails with 0.9.0 rc2. Bisecting.

@buchgr
Copy link
Contributor

buchgr commented Dec 8, 2017

git bisect tells me that 337f19c is the offending commit.

@buchgr
Copy link
Contributor

buchgr commented Dec 8, 2017

I reverted the commit on my local branch and can confirm that bazel-watcher works without the commit.

@laszlocsomor
Copy link
Contributor Author

See #3773 (comment)
Damien apparently already expected that change to cause problems. As I understand it, he planned to revert it anyway.

Jakob, can you revert that commit please?

@buchgr
Copy link
Contributor

buchgr commented Dec 8, 2017

Yes sir!

bazel-io pushed a commit that referenced this issue Dec 8, 2017
*** Reason for rollback ***

This breaks downstream projects and blocks Bazel's 0.9.0 release. See #4249 for more information.

*** Original change description ***

Move override check to the createAndOverrideRule function

So we actually test for override also from skylark repositories.

Fixes #3908.

Change-Id: I7650a17834a6915a73c89df46989f72aa2f56920
PiperOrigin-RevId: 178370143
laszlocsomor pushed a commit that referenced this issue Dec 8, 2017
*** Reason for rollback ***

This breaks downstream projects and blocks Bazel's 0.9.0 release. See #4249 for more information.

*** Original change description ***

Move override check to the createAndOverrideRule function

So we actually test for override also from skylark repositories.

Fixes #3908.

Change-Id: I7650a17834a6915a73c89df46989f72aa2f56920
PiperOrigin-RevId: 178370143
laszlocsomor pushed a commit that referenced this issue Dec 12, 2017
*** Reason for rollback ***

This breaks downstream projects and blocks Bazel's 0.9.0 release. See #4249 for more information.

*** Original change description ***

Move override check to the createAndOverrideRule function

So we actually test for override also from skylark repositories.

Fixes #3908.

Change-Id: I7650a17834a6915a73c89df46989f72aa2f56920
PiperOrigin-RevId: 178370143
laszlocsomor pushed a commit that referenced this issue Dec 12, 2017
*** Reason for rollback ***

This breaks downstream projects and blocks Bazel's 0.9.0 release. See #4249 for more information.

*** Original change description ***

Move override check to the createAndOverrideRule function

So we actually test for override also from skylark repositories.

Fixes #3908.

Change-Id: I7650a17834a6915a73c89df46989f72aa2f56920
PiperOrigin-RevId: 178370143
laszlocsomor pushed a commit that referenced this issue Dec 13, 2017
*** Reason for rollback ***

This breaks downstream projects and blocks Bazel's 0.9.0 release. See #4249 for more information.

*** Original change description ***

Move override check to the createAndOverrideRule function

So we actually test for override also from skylark repositories.

Fixes #3908.

Change-Id: I7650a17834a6915a73c89df46989f72aa2f56920
PiperOrigin-RevId: 178370143
luca-digrazia pushed a commit to luca-digrazia/DatasetCommitsDiffSearch that referenced this issue Sep 4, 2022
    *** Reason for rollback ***

    This breaks downstream projects and blocks Bazel's 0.9.0 release. See bazelbuild/bazel#4249 for more information.

    *** Original change description ***

    Move override check to the createAndOverrideRule function

    So we actually test for override also from skylark repositories.

    Fixes #3908.

    Change-Id: I7650a17834a6915a73c89df46989f72aa2f56920
    PiperOrigin-RevId: 178370143
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breakage P1 I'll work on this now. (Assignee required)
Projects
None yet
Development

No branches or pull requests

2 participants