Skip to content

Conversation

fgerodez
Copy link
Contributor

@fgerodez fgerodez commented May 27, 2023

Description (*)

When a JoinProcessor is called multiple times during a request the join definitions are only applied the first time. Subsequent calls will leave the collections unmodified.

Fixed Issues (if relevant)

  1. Fixes JoinProcessor caching issue #27504

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)
@m2-assistant
Copy link

m2-assistant bot commented May 27, 2023

Hi @fgerodez. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.

Add the comment under your pull request to deploy test or vanilla Magento instance:
  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:
  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests
  13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.


For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

@fgerodez
Copy link
Contributor Author

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

@engcom-Hotel engcom-Hotel added the Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. label May 30, 2023
@engcom-Hotel
Copy link
Contributor

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

@andrewbess
Copy link
Contributor

@magento run all tests

Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

Copy link
Contributor

@andrewbess andrewbess left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @fgerodez
Thank you for your contribution
Could you please check my suggestion and fix copyright?
Thank you in advance.

fgerodez and others added 2 commits January 28, 2024 10:06
…iteria/CollectionProcessor/JoinProcessorTest.php Co-authored-by: Andrii Beziazychnyi <a.beziazychnyi@atwix.com>
@andrewbess
Copy link
Contributor

@magento run all tests

@andrewbess
Copy link
Contributor

@magento run WebAPI Tests, Functional Tests CE, Functional Tests EE

@m2-community-project m2-community-project bot added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Mar 26, 2024
@engcom-Dash
Copy link
Contributor

@magento run all tests

@engcom-Dash
Copy link
Contributor

@magento run all tests

@engcom-Dash
Copy link
Contributor

@magento run Functional Tests B2B, Functional Tests EE

1 similar comment
@engcom-Dash
Copy link
Contributor

@magento run Functional Tests B2B, Functional Tests EE

@Priyakshic Priyakshic added the Project: Community Picked PRs upvoted by the community label Dec 11, 2024
@engcom-Charlie engcom-Charlie self-assigned this Jan 3, 2025
@engcom-Charlie
Copy link
Contributor

Hi @fgerodez and @andrewbess,

Thank you for the contribution!

As the review is pending, moving it back to Pending review.

Thank you!

@engcom-Hotel
Copy link
Contributor

@magento run all tests

@engcom-Hotel engcom-Hotel added the Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it label Jan 6, 2025
Copy link
Contributor

@engcom-Hotel engcom-Hotel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @fgerodez,
Thanks for the contribution!

Please fix the failed automated tests, specifically static test, and look into the review comments below.

Thanks

class JoinProcessorTest extends TestCase
{
/**
* @var \Magento\Framework\ObjectManagerInterface
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This qualifier can be replaced with an import. Import the ObjectManagerInterface and use it as below:

Suggested change
* @var \Magento\Framework\ObjectManagerInterface
* @var ObjectManagerInterface

protected function setUp(): void
{
$this->objectManager = \Magento\TestFramework\Helper\Bootstrap::getObjectManager();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here

Suggested change
$this->objectManager = \Magento\TestFramework\Helper\Bootstrap::getObjectManager();
$this->objectManager = Bootstrap::getObjectManager();

$collection1 = $this->getMockBuilder(AbstractDb::class)
->disableOriginalConstructor()
->getMockForAbstractClass();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The getMockForAbstractClass method has been deprecated, please use alternate method.


$collection2 = $this->getMockBuilder(AbstractDb::class)
->disableOriginalConstructor()
->getMockForAbstractClass();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The getMockForAbstractClass method has been deprecated, please use alternate method.

@engcom-Dash
Copy link
Contributor

@magento run all tests

@engcom-Dash
Copy link
Contributor

Hello @fgerodez, Thanks for the contribution!

Please fix the failed automated tests, specifically static test, and look into the review comments below.

Thanks

@engcom-Hotel: I have implemented the suggested changes and fixed the integration failures. Moving it back to Pending Review.

NOTE: The failed integration tests are not related to the PR changes and can also be seen in other PRs.

@engcom-Dash
Copy link
Contributor

@magento run Integration Tests, Functional Tests EE

@engcom-Dash
Copy link
Contributor

@magento run all tests

@engcom-Dash engcom-Dash self-assigned this Jan 8, 2025
@engcom-Dash
Copy link
Contributor

@magento run all tests

@engcom-Dash
Copy link
Contributor

@magento run Unit Tests, Integration Tests, Functional Tests EE, Functional Tests CE, Functional Tests B2B

@engcom-Dash
Copy link
Contributor

The Functional B2B, CE and Integration test failures are inconsistent or known issues in the last two builds and seem to be flaky. They neither part of PR nor failing because of the PR changes, hence moving it to Merge in Progress.

Integration Tests
Run 1: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/37550/b8d3b143ee2d4461466eaecbc06cc161/Integration/console-error-logs.html
image

Run 2: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/37550/e55d6635f7dbd475f5ca236ceeb1a535/Integration/console-error-logs.html
image

Known Issue:
AC-13584

Functional Tests B2B
Run 1: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/37550/96b61a594a1ae1c7207fe8403c36d94a/Functional/allure-report-b2b/index.html#categories/6ca9d315ebd9ab54dbe1fb9148ebdc1f/36fcf222bef58cb7/
image

Run 2: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/37550/d07cd9fc1b64f9dd7ff8631e39bb5c04/Functional/allure-report-b2b/index.html#categories/bfde7a9fcff9e79ffbe443fe2e9ee992/fa198996fe557e5/
image

Known Issue:
EndToEndB2CLoggedInUserTest: ACQE-7387

Functional Tests CE
Run 1: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/37550/3cae302f7a40c3a2881c4787e7dd82c5/Functional/allure-report-ce/index.html#categories/75b40a63f79830217aae704c6d6af940/110526e17ad16bfb/
image

Run 2: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/37550/feee1c963f5bf6397afbd7fba47476db/Functional/allure-report-ce/index.html#categories/e93c564a2dcd5e30ee0e0e811a828c2b/811cd8516b0a14be/
image

Known Issue:
StoreFrontAddOutOfStockProductToShoppingCartTest: ACQE-6818

@magento-devops-reposync-svc magento-devops-reposync-svc merged commit c93b59c into magento:2.4-develop Feb 17, 2025
9 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Award: test coverage Component: Framework/Component Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: accept Project: Community Picked PRs upvoted by the community Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
7 participants