-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-29787 Run Yetus General Checks as a GitHub Action #7566
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
base: master
Are you sure you want to change the base?
Conversation
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 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 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 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.
|
I think this is working. Please help me out by double-checking that the checks run by the new system have parity with the jenkins build. |
Let's just try it on a special branch? Scripts are always hard to review... |
|
Ah, I saw the checks, let me check the result... |
|
Seems we missed lots of checks... |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
🎊 +1 overall
This message was automatically generated. |
9f788ac to
074a452
Compare
|
🎊 +1 overall
This message was automatically generated. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
💔 -1 overall
This message was automatically generated. |
This comment has been minimized.
This comment has been minimized.
a93e175 to
0de876d
Compare
|
💔 -1 overall
This message was automatically generated. |
0de876d to
fba02bc
Compare
|
💔 -1 overall
This message was automatically generated. |
fba02bc to
e35b472
Compare
|
(!) A patch to the testing environment has been detected. |
|
Heya @aw-was-here . I'm pretty close on converting this general-check over to a GHA. The problem I'm having is that the failure reports are not linking back to the nightlies path where they are uploaded after the build. You can see an example of a broken link-back in #7566 (comment) / https://github.com/apache/hbase/actions/runs/20854644944 . I think this comes down to running in ROBOT mode but the githubaction robot doesn't implement the githubactions_artifact_url and there's no fall-back. I'm trying to validate this theory by adding this function to the personality file. The next build will show that result. Is this a bug or is it intentional behavior that I'm not using correctly? Thanks. |
|
💔 -1 overall
This message was automatically generated. |
This comment has been minimized.
This comment has been minimized.
|
(!) A patch to the testing environment has been detected. |
1 similar comment
|
(!) A patch to the testing environment has been detected. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
No description provided.