Skip to content
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

Ornery++ #29550

Merged
merged 3 commits into from
Mar 2, 2024
Merged

Ornery++ #29550

merged 3 commits into from
Mar 2, 2024

Conversation

eileenmcnaughton
Copy link
Contributor

@eileenmcnaughton eileenmcnaughton commented Feb 29, 2024

Overview

This flags some particularly slow tests in the apiv3SyntaxConfirmanceTest so they do not run on PR runs. These tests used to be a good little canaries but have grown soft & fat as we improved our code & no longer have the stamina to run several times a day in a timely manner

Before

On PRs submitted about the same time
image

image

After

On this PR apiv3 time taken

image

& with the second ornery

image

Technical Details

There are a couple of other tests we could do this to but with this change the apiv3 tests are faster than the crm test so there might not be much to gain from further apiv3 test speed improvements

Comments

Copy link

civibot bot commented Feb 29, 2024

🤖 Thank you for contributing to CiviCRM! ❤️ We will need to test and review this PR. 👷

Introduction for new contributors...
  • If this is your first PR, an admin will greenlight automated testing with the command ok to test or add to whitelist.
  • A series of tests will automatically run. You can see the results at the bottom of this page (if there are any problems, it will include a link to see what went wrong).
  • A demo site will be built where anyone can try out a version of CiviCRM that includes your changes.
  • If this process needs to be repeated, an admin will issue the command test this please to rerun tests and build a new demo site.
  • Before this PR can be merged, it needs to be reviewed. Please keep in mind that reviewers are volunteers, and their response time can vary from a few hours to a few weeks depending on their availability and their knowledge of this particular part of CiviCRM.
  • A great way to speed up this process is to "trade reviews" with someone - find an open PR that you feel able to review, and leave a comment like "I'm reviewing this now, could you please review mine?" (include a link to yours). You don't have to wait for a response to get started (and you don't have to stop at one!) the more you review, the faster this process goes for everyone 😄
  • To ensure that you are credited properly in the final release notes, please add yourself to contributor-key.yml
  • For more information about contributing, see CONTRIBUTING.md.
Quick links for reviewers...

➡️ Online demo of this PR 🔗

@eileenmcnaughton
Copy link
Contributor Author

test this please

@colemanw
Copy link
Member

colemanw commented Mar 1, 2024

@civicrm-builder retest this please

@colemanw
Copy link
Member

colemanw commented Mar 1, 2024

api_v3_SystemCheckTest::testSystemCheckBasic with data set "APIv3" (3)
Exception: CRM_Core_Exception: "checkDefaultMailbox not in results"

@eileenmcnaughton I suspect the test failure has to do with the component not being enabled. Probably the syntax conformance tests would enable all components & then other tests would just blithely assume they are always enabled.

@eileenmcnaughton
Copy link
Contributor Author

@colemanw that makes sense - I had concluded the test was not improving things as much as I hoped (the screenshots above are not consistent) & that the one that creates the custom data sets might be a bigger win - but then all these tests .....

@eileenmcnaughton
Copy link
Contributor Author

@colemanw I got it!

@colemanw colemanw merged commit 9743887 into civicrm:master Mar 2, 2024
3 checks passed
@colemanw colemanw deleted the those_orns branch March 2, 2024 22:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants