Performance tests tooling : Compare performance with correct branch#66196
Performance tests tooling : Compare performance with correct branch#66196cbravobernal merged 2 commits intotrunkfrom
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Thanks for the fix 🙂 I wasn't sure why the performance tests were failing in manual cherry picks like this one: link. |
|
I just cherry-picked this PR to the wp/6.7 branch to get it included in the next release: f98cdf7 |
…6196) * Target base branch instead of just trunk * Update description Co-authored-by: cbravobernal <cbravobernal@git.wordpress.org> Co-authored-by: youknowriad <youknowriad@git.wordpress.org>
|
Warning: Type of PR label mismatch To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.
Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task. |
…rdPress#66196) * Target base branch instead of just trunk * Update description Co-authored-by: cbravobernal <cbravobernal@git.wordpress.org> Co-authored-by: youknowriad <youknowriad@git.wordpress.org>
What?
Target Performance tests to base branch instead of just Trunk.
Why?
If
trunkdiffers from another base branch, likewp/6.7, changing for example selectors. Performance tests will fail on all cherry picks to releases branches.Testing Instructions
I'll make this PR to 6.7 to see if performance is being executed there.