Integration test failure during product export

[magento-engcom-team]

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

[magento-engcom-team]

The issue was exported from the internal JIRA. The link to the original JIRA issue: https://jira.corp.magento.com/browse/SFAPP-178

[m2-assistant]

Hi @magento-engcom-team. Thank you for your report.
To help us process this issue please make sure that you provided sufficient information.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.