-
Couldn't load subscription status.
- Fork 3.4k
HBASE-26542 Apply a package to test protobuf files
#3924
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
Conversation
|
@busbey any idea if test-patch will pick up on the protobuf change and run unit tests in affected modules? |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
To answer my own question, the answer appears to be, "sort of".
|
|
So there's a direct dependency, but |
|
Comparing the output here vs. other PRs I have up, this one seems to be missing section "maven install: master". Maybe this needs added to |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
0a7f96f to
2867035
Compare
This comment has been minimized.
This comment has been minimized.
2 similar comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
This is better. It didn't run any tests impacted by the changed protoc files, but it didn't fail either. |
|
So which PR is effected? In the past we have a lot of PRs which changes the protobuf files but I haven't seen any problems on the pre commit run... |
|
The primary change on this PR (HBASE-26542) is a change to the test protoc files. pre-commit did not handle the change properly and errored out (see the initial jenkins build). I pushed a second commit here, the same commit as is on #3927 / HBASE-26549, which tweaks the This PR/HBASE-26542 is need in order to test inclusion of protoc service package names in HBASE-26521 . |
|
What I mean is that, we used to change the protobuf files a lot in the past and IIRC we haven't seen any problems on the pre commit build. So I want to know, in which PR you see a broken pre commit result because of the problem the described here? It seems that we do not run 'mvn install' first then the build will be broken? Thanks. |
@Apache9 This same PR is where the problem was seen. See the results of the first CI checks for full details. The exact error I extracted from the build log and posted in this comment,
One difference between this and previous changes to protobuf files may be that this PR is changing the test protobuf files, not the main ones. |
|
OK, I guess the problem is that if we only touch the proto without changing any java files, we will not trigger a 'mvn install' first which could lead to the problem... Let me take a look at the PR here, thanks @ndimiduk for explaining. |
2867035 to
031b63f
Compare
Oh, of course! Yes, that makes perfect sense. Thanks for taking a look. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
This is needed in a couple places in order to test that traces over the IPC layer carry correct span names, and it's good hygiene anyway. Signed-off-by: Duo Zhang <[email protected]>
031b63f to
6865cbc
Compare
This is needed in a couple places in order to test that traces over the IPC layer carry correct
span names, and it's good hygiene anyway.