Skip to content

[Backport] Stabilize Travis CI integration tests suite #16935

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

Closed
wants to merge 1 commit into from
Closed

[Backport] Stabilize Travis CI integration tests suite #16935

wants to merge 1 commit into from

Conversation

mageprince
Copy link
Contributor

Original Pull Request

#16909

Description

Travis CI integration test suites for 2.3-develop branch are frequently failing with timeout on integration batch 2. This is caused by incorrect distribution of the tests across suites, where suite 1 runs for just 11 minutes, and suite 2 runs for up to 50 minutes.

This Pull Request changes this distribution to spread execution time more evenly between batches 1, 2 and 3.

Reference build result: https://travis-ci.org/ishakhsuvarov/magento2/builds/405247843

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)
  • All automated tests passed successfully (all builds on Travis CI are green)

 - Updated test distribution between integration test suites
@magento-engcom-team
Copy link
Contributor

Hi @mageprince. Thank you for your contribution
Here is some useful tips 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-engcom-team give me test instance - deploy test instance based on PR changes
  • @magento-engcom-team give me {$VERSION} instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

@osrecio osrecio self-assigned this Jul 19, 2018
@osrecio
Copy link
Member

osrecio commented Jul 19, 2018

@mageprince Thanks for your Backport.

@ishakhsuvarov You think that this PR is applied to 2.2-develop if is only for distribution of the tests suites of branch 2.3-develop ?

@sidolov sidolov self-assigned this Jul 19, 2018
@sidolov
Copy link
Contributor

sidolov commented Jul 19, 2018

Hi @mageprince , this changes was addressed to 2.3 release line only and not applicable for 2.2 release line. I'm closing this PR as not relevant.

@sidolov sidolov closed this Jul 19, 2018
@ishakhsuvarov
Copy link
Contributor

@osrecio I explicitly mentioned in the description that it relates to 2.3. Currently I don't see same problem with other release lines

@mageprince mageprince deleted the 2.2-develop-PR-port-16909 branch July 19, 2018 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants