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

[Issue] Removed usage of CliIndexerReindexActionGroup action group for Catalog module #31233

Closed
m2-assistant bot opened this issue Dec 9, 2020 · 1 comment · Fixed by #31228
Closed
Assignees
Labels
Component: Catalog Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done Progress: PR in progress Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.

Comments

@m2-assistant
Copy link

m2-assistant bot commented Dec 9, 2020

This issue is automatically created based on existing pull request: #31228: Removed usage of CliIndexerReindexActionGroup action group for Catalog module


Description

Remove usage or changed value of CliIndexerReindexActionGroup action group from tests to improve execution time for the Catalog module.

@m2-assistant m2-assistant bot added Component: Catalog Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Dec 9, 2020
@magento-engcom-team
Copy link
Contributor

Hi @m2-assistant[bot]. Thank you for your report.
The issue has been fixed in #31228 by @sergiy-v in 2.4-develop branch
Related commit(s):

The fix will be available with the upcoming 2.4.3 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Catalog Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done Progress: PR in progress Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
Status: Pull Request In Progress
Development

Successfully merging a pull request may close this issue.

2 participants