Skip to content

Remove bazel from repo #4297

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

Merged
merged 5 commits into from
Jul 9, 2021
Merged

Conversation

MichaelBroughton
Copy link
Collaborator

Fixes #4280

@MichaelBroughton MichaelBroughton requested a review from balopat July 7, 2021 20:52
@MichaelBroughton MichaelBroughton requested review from cduck, vtomole and a team as code owners July 7, 2021 20:52
@google-cla google-cla bot added the cla: yes Makes googlebot stop complaining. label Jul 7, 2021
bazel build "${base}_py_proto"; \
bazel build "${base}_cc_proto")

python -m grpc_tools.protoc -I=cirq-google --python_out=cirq-google --mypy_out=cirq-google ${base}.proto
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is useful to have a job that checks for whether the checked-in pb2 files are up to date with the protos or not. Thus, we should keep the grpc_tools generation part. Also, this might be a good point to clean up the duplication between this job and dev_tools/build-protos.sh.

Copy link
Contributor

@balopat balopat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for picking this up! I'd keep a simplified version of the build-changed-protos job.

@MichaelBroughton
Copy link
Collaborator Author

MichaelBroughton commented Jul 7, 2021

How do you propose we keep an alternate version of the build-changed-protos job ? Reading through it a little more closely I'm actually a little surprised we had it in the first place. All it really did was build the protos against the current version of grpcio. It did no follow up tests or version checks of any kind against other parts of the library (that I can find).

Are you thinking we add some kind of test that actually builds new pb2 files from the .proto files on the repo and do some functionality tests there ?

@balopat
Copy link
Contributor

balopat commented Jul 7, 2021

How do you propose we keep an alternate version of the build-changed-protos job ? Reading through it a little more closely I'm actually a little surprised we had it in the first place. All it really did was build the protos against the current version of grpcio. It did no follow up tests or version checks of any kind against other parts of the library (that I can find).

Are you thinking we add some kind of test that actually builds new pb2 files from the .proto files on the repo and do some functionality tests there ?

This script did test whether the proto definitions are consistent with the pb2 files or not, based on the assumption that previously they were. If that assumption is true, and the proto files change, the pb2 files might change. In that case the developer should commit the new version of the pb2 file. If they forgot to do that, these lines check whether there is a change simply using git after rebuilding the pb2 files using grpcio:

https://github.com/quantumlib/Cirq/pull/4297/files#diff-bc40ce42a88c1b3c04e7c0248a1094cf47ad7b088e6f549c0b8987dfb4ff1e91L100-L112

@balopat
Copy link
Contributor

balopat commented Jul 7, 2021

@MichaelBroughton
Copy link
Collaborator Author

Ok, so do we want to just keep these "change checker" style of tests from the build-changed-protos and leave it at that then ?

@balopat
Copy link
Contributor

balopat commented Jul 8, 2021

Ok, so do we want to just keep these "change checker" style of tests from the build-changed-protos and leave it at that then ?

Yes!

@balopat balopat self-assigned this Jul 8, 2021
Copy link
Contributor

@balopat balopat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@balopat balopat added the automerge Tells CirqBot to sync and merge this PR. (If it's running.) label Jul 9, 2021
@CirqBot CirqBot added the front_of_queue_automerge CirqBot uses this label to indicate (and remember) what's being merged next. label Jul 9, 2021
@CirqBot
Copy link
Collaborator

CirqBot commented Jul 9, 2021

Automerge cancelled: A required status check is not present.

Missing statuses: ['Changed files test', 'Format check']

@CirqBot CirqBot removed automerge Tells CirqBot to sync and merge this PR. (If it's running.) front_of_queue_automerge CirqBot uses this label to indicate (and remember) what's being merged next. labels Jul 9, 2021
@MichaelBroughton MichaelBroughton added the automerge Tells CirqBot to sync and merge this PR. (If it's running.) label Jul 9, 2021
@CirqBot CirqBot added the front_of_queue_automerge CirqBot uses this label to indicate (and remember) what's being merged next. label Jul 9, 2021
@CirqBot CirqBot merged commit 418d067 into quantumlib:master Jul 9, 2021
@CirqBot CirqBot removed automerge Tells CirqBot to sync and merge this PR. (If it's running.) front_of_queue_automerge CirqBot uses this label to indicate (and remember) what's being merged next. labels Jul 9, 2021
@MichaelBroughton MichaelBroughton deleted the remove_bazel branch July 9, 2021 02:39
rht pushed a commit to rht/Cirq that referenced this pull request May 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes Makes googlebot stop complaining.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove bazel
3 participants