-
Notifications
You must be signed in to change notification settings - Fork 19
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
Update test run generator script #298
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM; thanks for doing this, @srirambv 👍
- [ ] Navigate to `/Users/<user>/Library/Application Support/BraveSoftware/Brave-Browser-<channel>/cldoidikboihgcjfkhdeidbpclkineef/<version>` | ||
- [ ] Run `codesign -vvvv tor-<version-tor>-darwin-brave-<version-brave>` to confirm codesign is valid | ||
- [ ] For MacOS Catalina (10.15+) - Run `spctl -a -vv -t install tor-<version-tor>-darwin-brave-<version-brave>` to verify that the binary is notarized. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if copy/paste error, but Catalina
isn't listed, should be between Big Sur
and Mojave
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That was copy paste from one of the test runs.
@srirambv there's also an issue when attempting to generate passes for the current After selecting
However, it runs into the following issue and never ends up creating the GH issues:
It looks like Definitely not an authentication issues as I managed to create the manual passes for |
I personally think we can remove
I think most of the team knows how to use GH search queries to check and see what's left in each milestone for a specific platform. @LaurenWags @GeetaSarvadnya @StephenBass @btlechowski thoughts? |
@srirambv still reviewing, it will probably take a bit as there's a lot of changes and we'll probably want to make sure these are actually being created on GH to flush out possible issues as mentioned via #298 (comment). |
++ on removing |
This is fixed. Was an issue with assignee's list. Also generated the test runs via the script https://github.com/brave/brave-browser/milestones/1.25.x%20-%20Release%20%235 This is also fixed. Removed the |
Thoughts not pre-assigning passes? Most of the time everyone knows the pass they're going to run through so they can just assign it to themselves when they start them. There's cases where someone else grabs them instead of the pre-assigned person. For example, I usually run through the Another example would be iOS passes. Sometimes someone else might run through the ones that have already been assigned to @srirambv if @srirambv is running through verification or is busy doing something else. I think the general rule should be: If you're starting a manual pass, you assign it to yourself so the QA team knows that someone claimed the work/pass and is running through it. It also might avoid confusion as well re: someone thinking that because it's already assigned, it means they can't start it even though the person that is assigned the pass might not even have plans to start it any time soon. @LaurenWags @GeetaSarvadnya @stephendonner @btlechowski thoughts? |
I don't think the issue assignment's a big deal. Its pretty trivial. Everybody knows what they usually run so its easier to assign when they start. And since we always communicate internally when someone else is being asked to run they can just self assign then and remove the original assignee. I am ok to remove it if everyone agrees but feel its unnecessary. We anyways do assign now even when we create the issues manually |
++ on removing |
my test runs usually come pre-assigned, but I figured that's just because I'm currently the only person with M1 and Android x86 😄 I'm fine either way re: assignment and happy to go with whatever is easiest for all. |
I only assign Lets just remove the pre-assigns as it's more intuitive rather than re-assigning. We can leave @LaurenWags as the assignee for |
Lets remove |
Ok removed default assignee for all test runs. people can self assign when they run. Also updated x86 test template. Should be good enough now |
@srirambv small nit: mind adding the I'll create manual passes for |
Added Tor labels. Should be ready for merge |
@srirambv need to change the label for the |
Done |
@srirambv could you update the
reference: https://bravesoftware.slack.com/archives/GAA4017R7/p1623759655029000 |
@srirambv can you update the
|
@srirambv while @kjozwiak was helping me get set up we talked about needing to change the This is the "installer" section macOS (intel) needs:
wdyt? |
@srirambv lets rename the
Example: brave/brave-browser#16413 |
I'd suggest we address the template changes in #312 with a follow up PR. This one is more for the script. I updated the Tor and desktop suggestions. If there is nothing else I'd like to get this merged and do a follow up for other changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Nice work. We'll handle the template changes in another PR as you mentioned above.
Fixes #183
Changes include: