magento / magento/catalog-storefront

Integration test failure during product export

Open
#461 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Progress: backlog Severity: Critical
Dominant language
PHP
Stars
7
Forks
16
PR merge metrics
No merged PRs in 30d

Description

GenerateFixturesCommandTest failures after the latest merges. 

The latest run on storefront can be found here:

https://github.com/magento-commerce/catalog-storefront-ce/pull/20/checks?check*run*id=1519055911

http://10.234.226.254:8080/job/Integration-Tests/5721/testReport/junit/Magento.Setup.Console.Command/GenerateFixturesCommandTest/testExecute/

StacktraceMagento\Setup\Console\Command\GenerateFixturesCommandTest::testExecute 
Design Config Grid index has been rebuilt successfully in 00:00:00 
Customer Grid index has been rebuilt successfully in 00:00:00 
Category Products index has been rebuilt successfully in 00:00:00 
Product Categories index has been rebuilt successfully in 00:00:00 
Catalog Rule Product index has been rebuilt successfully in 00:00:00 
Product EAV index has been rebuilt successfully in 00:00:00 
Product Price index has been rebuilt successfully in 00:00:00 
Product Attributes Feed index has been rebuilt successfully in 00:00:00 
Category Feed index has been rebuilt successfully in 00:00:00 
Stock index has been rebuilt successfully in 00:00:00 
Catalog Product Rule index has been rebuilt successfully in 00:00:00 
Product Feed index process unknown error: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away 

https://github.com/magento-commerce/magento2ce/pull/6436/checks?check_run_id=1526500160
run with debug shows that max_allowed_packet=16M, that is not enough for products to be exported.

To reproduce issue on local machine set the following value in your local MySQL config:
max_allowed_packet = 16M
and run Setup\Console\Command\GenerateFixturesCommandTest::testExecute

AC:
Tests must be green

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with Setup\Console\Command\GenerateFixturesCommandTest::testExecute and reproduce the failure using a local MySQL configuration with max_allowed_packet = 16M. Review the linked CI output and stack trace, then confirm the test completes successfully and the integration test suite is green.

Written by the indexing model from the issue text.

Assessment

Tech stack
mysql, php
Domain
backend, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.