magento / ece-tools

All Submissions you make to Magento Inc. (“Magento") through GitHub are subject to the following terms and conditions: (1) You grant Magento a perpetual, worldwide, non-exclusive, no charge, royalty free, irrevocable license under your applicable copyrights and patents to reproduce, prepare derivative works of, display, publically perform, sublicense and distribute any feedback, ideas, code, or other information (“Submission") you submit through GitHub. (2) Your Submission is an original work of authorship and you are the owner or are legally entitled to grant the license stated above. (3) You agree to the Contributor License Agreement found here: https://github.com/magento/magento2/blob/master/CONTRIBUTOR_LICENSE_AGREEMENT.html
Open Software License 3.0
117 stars 83 forks source link

Feature/resolve autoload #799

Closed leonhelmus closed 3 years ago

leonhelmus commented 3 years ago

When deploying to a feature environment with parent integration i get the following error: CRITICAL: [9] Required configuration is missed in autoload section of composer.json file. Add ("Laminas\Mvc\Controller\: "setup/src/Zend/Mvc/Controller/") to autoload -> psr-4 section and re-run "composer update" command locally. Then commit new composer.json and composer.lock files., but when i look in the code base of magento 2.4.3: https://github.com/magento/magento2/blob/2.4.3/composer.json and compare it to 2.4.2. "Laminas\Mvc\Controller\: "setup/src/Zend/Mvc/Controller/" was removed on purpose in the upgrade.

Preconditions

  1. M2.4.3, PHP 7.4, MariaDB 10.4, Redis 5.0, composer 1
  2. Deploy to any magento cloud environment using magento-cloud environment:push

Steps to reproduce

  1. Upgrade magento cloud to 2.4.3 ("magento/magento-cloud-metapackage": ">=2.4.3 <2.4.4")
  2. Use composer root update plugin to update your composer.json with the latest changes using: composer require magento/product-enterprise-edition:2.4.3 --base-magento-edition 'Commerce' --base-magento-version 2.4.2-p1 --no-update
  3. Upgrade magento using composer update.
  4. After everything has been succesfully upgraded deploy to a feature env that has integration as a parent.
  5. Deployment gives the following error: `Executing build hook... [2021-08-26 09:29:00] INFO: Starting scenario(s): scenario/build/generate.xml (magento/ece-tools version: 2002.1.7, magento/magento2-base version: 2.4.3) [2021-08-26 09:29:02] INFO: Verbosity level is not set [2021-08-26 09:29:02] NOTICE: Applying patches [2021-08-26 09:29:03] NOTICE: End of applying patches [2021-08-26 09:29:03] INFO: Set Magento application mode to 'production' [2021-08-26 09:29:03] NOTICE: Validating configuration [2021-08-26 09:29:03] NOTICE: Fix configuration with given suggestions: [2021-08-26 09:29:03] CRITICAL: [9] Required configuration is missed in autoload section of composer.json file. Add ("Laminas\Mvc\Controller\: "setup/src/Zend/Mvc/Controller/") to autoload -> psr-4 section and re-run "composer update" command locally. Then commit new composer.json and composer.lock files. [2021-08-26 09:29:03] ERROR: [9] Required configuration is missed in autoload section of composer.json file. W: W: In Processor.php line 129: W:
    W: Required configuration is missed in autoload section of composer.json file.
    W:
    W: W: In ValidateConfiguration.php line 69: W:
    W: Required configuration is missed in autoload section of composer.json file.
    W:
    W: W: build:generate W:

    E: Error building project: Step failed with status code 9.

E: Error: Unable to build application, aborting.`

Expected result

deploys correctly without errors.

Actual result

  1. [Screenshots, logs or description] image
magento-cloud-ft-jenkins-svc commented 3 years ago

Unit & Integration Test Results

:x:  One or more unit or integration tests have failed.

Unit Test Output

> phpunit --configuration tests/unit '--log-junit' 'tests/unit/tmp/junit.xml' '--coverage-clover' 'tests/unit/tmp/clover.xml'
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.

.............................................................   61 / 1511 (  4%)
.............................................................  122 / 1511 (  8%)
.............................................................  183 / 1511 ( 12%)
.............................................................  244 / 1511 ( 16%)
.............................................................  305 / 1511 ( 20%)
.............................................................  366 / 1511 ( 24%)
.............................................................  427 / 1511 ( 28%)
.............................................................  488 / 1511 ( 32%)
.FFF.F.......................................................  549 / 1511 ( 36%)
.............................................................  610 / 1511 ( 40%)
.............................................................  671 / 1511 ( 44%)
.............................................................  732 / 1511 ( 48%)
.............................................................  793 / 1511 ( 52%)
.............................................................  854 / 1511 ( 56%)
.............................................................  915 / 1511 ( 60%)
.............................................................  976 / 1511 ( 64%)
............................................................. 1037 / 1511 ( 68%)
............................................................. 1098 / 1511 ( 72%)
............................................................. 1159 / 1511 ( 76%)
............................................................. 1220 / 1511 ( 80%)
............................................................. 1281 / 1511 ( 84%)
............................................................. 1342 / 1511 ( 88%)
............................................................. 1403 / 1511 ( 92%)
............................................................. 1464 / 1511 ( 96%)
...............................................               1511 / 1511 (100%)

Time: 17.24 seconds, Memory: 82.50 MB

There were 4 failures:

1) Magento\MagentoCloud\Test\Unit\Config\Validator\Build\ComposerFileTest::testValidateCorrectComposerJson
Magento\MagentoCloud\Package\MagentoVersion::isGreaterOrEqual('2.4.3'): bool was not expected to be called more than once.

/var/jenkins/workspace/ece-tools/unit/src/Config/Validator/Build/ComposerFile.php:87
/var/jenkins/workspace/ece-tools/unit/src/Test/Unit/Config/Validator/Build/ComposerFileTest.php:85

2) Magento\MagentoCloud\Test\Unit\Config\Validator\Build\ComposerFileTest::testValidateCorrectLaminasComposerJson
Magento\MagentoCloud\Package\MagentoVersion::isGreaterOrEqual('2.4.3'): bool was not expected to be called more than once.

/var/jenkins/workspace/ece-tools/unit/src/Config/Validator/Build/ComposerFile.php:87
/var/jenkins/workspace/ece-tools/unit/src/Test/Unit/Config/Validator/Build/ComposerFileTest.php:103

3) Magento\MagentoCloud\Test\Unit\Config\Validator\Build\ComposerFileTest::testValidateWrongComposerJson
Magento\MagentoCloud\Package\MagentoVersion::isGreaterOrEqual('2.4.3'): bool was not expected to be called more than once.

/var/jenkins/workspace/ece-tools/unit/src/Config/Validator/Build/ComposerFile.php:87
/var/jenkins/workspace/ece-tools/unit/src/Test/Unit/Config/Validator/Build/ComposerFileTest.php:132

4) Magento\MagentoCloud\Test\Unit\Config\Validator\Build\ComposerFileTest::testValidateComposerFileNotExists
Magento\MagentoCloud\Package\MagentoVersion::isGreaterOrEqual('2.4.3'): bool was not expected to be called more than once.

/var/jenkins/workspace/ece-tools/unit/src/Config/Validator/Build/ComposerFile.php:87
/var/jenkins/workspace/ece-tools/unit/src/Test/Unit/Config/Validator/Build/ComposerFileTest.php:172

FAILURES!
Tests: 1511, Assertions: 4743, Failures: 4.

Generating code coverage report in Clover XML format ... done
Script phpunit --configuration tests/unit handling the test:unit event returned with error code 1

Integration Test Output

> phpunit --configuration tests/integration '--log-junit' 'tests/integration/tmp/junit.xml'
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.

................................................................. 65 / 65 (100%)

Time: 3.81 seconds, Memory: 28.00 MB

OK (65 tests, 69 assertions)

This comment was generated by Jenkins job ece-tools/unit build 32.

magento-cloud-ft-jenkins-svc commented 3 years ago

Static Analysis & Code Style Results

:white_check_mark:  All static analysis and code style checks have passed.

PHP Codesniffer Output

> phpcs src --standard=tests/static/phpcs-ruleset.xml -p -n
............................................................  60 / 702 (9%)
............................................................ 120 / 702 (17%)
............................................................ 180 / 702 (26%)
............................................................ 240 / 702 (34%)
............................................................ 300 / 702 (43%)
............................................................ 360 / 702 (51%)
............................................................ 420 / 702 (60%)
............................................................ 480 / 702 (68%)
............................................................ 540 / 702 (77%)
............................................................ 600 / 702 (85%)
............................................................ 660 / 702 (94%)
..........................................                   702 / 702 (100%)

Time: 26.44 secs; Memory: 24MB

PHP Mess Detector Output


Found 0 violations and 0 errors in 22676ms

No mess detected

PHPStan Output

> phpstan analyse -c tests/static/phpstan.neon '--no-progress'

 [OK] No errors                                                                 

This comment was generated by Jenkins job ece-tools/static build 31.

magento-cloud-ft-jenkins-svc commented 3 years ago

Functional Acceptance Test Results

:x:  One or more functional acceptance tests have failed.

PHP 7.1

PHP 7.2

PHP 7.3

PHP 7.4

Output for failed tests is below. If many tests have failed only the first 5 will be included. If you need additional information please reach out to the Magento Cloud team for more details.

This comment was generated by Jenkins job ece-tools/functional build 53.

magento-cloud-ft-jenkins-svc commented 3 years ago

PHP 7.2 RedisPhp72Cest Output

Codeception PHP Testing Framework v2.5.6
Powered by PHPUnit 7.5.20 by Sebastian Bergmann and contributors.
Running with seed: 

Acceptance Tests (7) ---------------------------------------
RedisPhp72Cest: Test good configuration
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72Cest:testGoodConfiguration
Test: src/Test/Functional/Acceptance/RedisPhp72Cest.php:testGoodConfiguration
Scenario --
 SKIPPED 
RedisPhp72Cest: Test default configuration | "2.2.11"
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72Cest:testDefaultConfiguration
Test: src/Test/Functional/Acceptance/RedisPhp72Cest.php:testDefaultConfiguration
Scenario --
 I cleanup work dir 
 I is cache work dir exists "2.2.11"
 I clone template to work dir "2.2.11"
 I create auth json 
 I create artifacts dir 
 I create artifact current tested code "ece-t...","2002...."
 I add artifacts repo to composer 
 I add dependency to composer "magento/ece-t...","2002.1.99"
 I add ece docker git repo to composer 
 I add cloud components git repo to composer 
 I add cloud patches git repo to composer 
 I add quality patches git repo to composer 
 I get dependency version "magento/magento-cloud-docker"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-components"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-patches"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/quality-patches"
 I add dependency to composer "magento/q...","dev-maste..."
 I assert true true,"Can not add dependency magento/qual..."
 I composer update 
 I assert true true,"Composer update failed"
 I cache work dir "2.2.11"
sh: rsync: not found
 I read services yaml 
 I write services yaml {"mysql":{"type":"mysql:10.2","di...}
 I read app magento yaml 
 I write app magento yaml {"name":"mymagento","type":"ph...}
 I get exposed port 
 I generate docker compose "--mode=production --expose-d..."
 I run docker compose command "run build cloud-build"
 I assert true true,"Build phase was failed"
 I start environment 
 I assert true true,"Docker could not start"
 I run docker compose command "run deploy cloud-deploy"
 I assert true true,"Deploy phase was failed"
 I run docker compose command "run deploy cloud-post-deploy"
 I assert true true,"Post Deploy phase was failed"
 I download from container "/app/e...","/tmp/a...","deploy"
 I assert true true
 I assert same "Cm_Cache_...","Cm_Cache_...","Wrong bac..."
 I assert array subset {"backend_opti...},{"backend":"Cm...}
 I assert same "Cm_Cache_...","Cm_Cache_...","Wrong bac..."
 I assert array subset {"backend_opti...},{"backend":"Cm...}
 I assert array not has key "type",{"frontend":{"default...}
 I am on page "/"
 I see "Home page"
 I see "CMS homepage content goes here."
 I stop environment 
 I remove work dir 
 PASSED 

RedisPhp72Cest: Test default configuration | "2.3.0"
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72Cest:testDefaultConfiguration
Test: src/Test/Functional/Acceptance/RedisPhp72Cest.php:testDefaultConfiguration
Scenario --
 I cleanup work dir 
 I is cache work dir exists "2.3.0"
 I clone template to work dir "2.3.0"
 I create auth json 
 I create artifacts dir 
 I create artifact current tested code "ece-t...","2002...."
 I add artifacts repo to composer 
 I add dependency to composer "magento/ece-t...","2002.1.99"
 I add ece docker git repo to composer 
 I add cloud components git repo to composer 
 I add cloud patches git repo to composer 
 I add quality patches git repo to composer 
 I get dependency version "magento/magento-cloud-docker"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-components"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-patches"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/quality-patches"
 I add dependency to composer "magento/q...","dev-maste..."
 I assert true true,"Can not add dependency magento/qual..."
 I composer update 
 I assert true true,"Composer update failed"
 I cache work dir "2.3.0"
sh: rsync: not found
 I read services yaml 
 I write services yaml {"mysql":{"type":"mysql:10.2","di...}
 I read app magento yaml 
 I write app magento yaml {"name":"mymagento","type":"ph...}
 I get exposed port 
 I generate docker compose "--mode=production --expose-d..."
 I run docker compose command "run build cloud-build"
 I assert true true,"Build phase was failed"
 I start environment 
 I assert true true,"Docker could not start"
 I run docker compose command "run deploy cloud-deploy"
 I assert true true,"Deploy phase was failed"
 I run docker compose command "run deploy cloud-post-deploy"
 I assert true true,"Post Deploy phase was failed"
 I download from container "/app/e...","/tmp/a...","deploy"
 I assert true true
 I assert same "Cm_Cache_...","Cm_Cache_...","Wrong bac..."
 I assert array subset {"backend_opti...},{"backend":"Cm...}
 I assert same "Cm_Cache_...","Cm_Cache_...","Wrong bac..."
 I assert array subset {"backend_opti...},{"backend":"Cm...}
 I assert array not has key "type",{"frontend":{"default...}
 I am on page "/"
 I see "Home page"
 I stop environment 
 I remove work dir 
 FAIL 

------------------------------------
Message: Failed asserting that  on page /
-->  Warning: Redis::connect(): php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution in /app/vendor/colinmollenhour/credis/Client.php on line 456 Warning: Redis::connect(): php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution in /app/vendor/col
[Content too long to display. See complete response in '/app/tests/functional/_output/' directory]
--> contains "Home page".
------------------------------------
Stack Trace: 
#0 /app/vendor/phpunit/phpunit/src/Framework/Constraint/Constraint.php(60): PHPUnit\Framework\Constraint\Constraint->fail(' Warning: Redis...', '')
#1 /app/vendor/phpunit/phpunit/src/Framework/Assert.php(2307): PHPUnit\Framework\Constraint\Constraint->evaluate(' Warning: Redis...', '')
#2 /app/vendor/codeception/codeception/src/Codeception/Util/Shared/Asserts.php(311): PHPUnit\Framework\Assert::assertThat(' Warning: Redis...', Object(Codeception\PHPUnit\Constraint\Page), '')
#3 /app/vendor/codeception/codeception/src/Codeception/Lib/InnerBrowser.php(1704): Codeception\Module->assertThat(' Warning: Redis...', Object(Codeception\PHPUnit\Constraint\Page), '')
#4 /app/vendor/codeception/codeception/src/Codeception/Lib/InnerBrowser.php(480): Codeception\Lib\InnerBrowser->assertPageContains('Home page')
#5 [internal function]: Codeception\Lib\InnerBrowser->see('Home page')
#6 /app/vendor/codeception/codeception/src/Codeception/Step.php(265): call_user_func_array(Array, Array)
#7 /app/vendor/codeception/codeception/src/Codeception/Scenario.php(72): Codeception\Step->run(Object(Codeception\Lib\ModuleContainer))
#8 /app/vendor/magento/magento-cloud-docker/tests/functional/_support/_generated/CliTesterActions.php(1538): Codeception\Scenario->runStep(Object(Codeception\Step\Assertion))
#9 /app/src/Test/Functional/Acceptance/RedisCest.php(92): CliTester->see('Home page')
#10 [internal function]: Magento\MagentoCloud\Test\Functional\Acceptance\RedisCest->testDefaultConfiguration(Object(CliTester), Object(Codeception\Example))
#11 /app/vendor/codeception/codeception/src/Codeception/Lib/Di.php(127): ReflectionMethod->invokeArgs(Object(Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72Cest), Array)
#12 /app/vendor/codeception/codeception/src/Codeception/Test/Cest.php(138): Codeception\Lib\Di->injectDependencies(Object(Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72Cest), 'testDefaultConf...', Array)
#13 /app/vendor/codeception/codeception/src/Codeception/Test/Cest.php(147): Codeception\Test\Cest->invoke('testDefaultConf...', Array)
#14 /app/vendor/codeception/codeception/src/Codeception/Test/Cest.php(82): Codeception\Test\Cest->executeTestMethod(Object(CliTester))
#15 /app/vendor/codeception/codeception/src/Codeception/Test/Test.php(89): Codeception\Test\Cest->test()
#16 /app/vendor/phpunit/phpunit/src/Framework/TestSuite.php(746): Codeception\Test\Test->run(Object(PHPUnit\Framework\TestResult))
#17 /app/vendor/codeception/phpunit-wrapper/src/Runner.php(118): PHPUnit\Framework\TestSuite->run(Object(PHPUnit\Framework\TestResult))
#18 /app/vendor/codeception/codeception/src/Codeception/SuiteManager.php(158): Codeception\PHPUnit\Runner->doEnhancedRun(Object(Codeception\Suite), Object(PHPUnit\Framework\TestResult), Array)
#19 /app/vendor/codeception/codeception/src/Codeception/Codecept.php(192): Codeception\SuiteManager->run(Object(Codeception\PHPUnit\Runner), Object(PHPUnit\Framework\TestResult), Array)
#20 /app/vendor/codeception/codeception/src/Codeception/Codecept.php(159): Codeception\Codecept->runSuite(Array, 'Acceptance', 'RedisPhp72Cest')
#21 /app/vendor/codeception/codeception/src/Codeception/Command/Run.php(384): Codeception\Codecept->run('Acceptance', 'RedisPhp72Cest', Array)
#22 /app/vendor/symfony/console/Command/Command.php(255): Codeception\Command\Run->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#23 /app/vendor/symfony/console/Application.php(1009): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#24 /app/vendor/symfony/console/Application.php(273): Symfony\Component\Console\Application->doRunCommand(Object(Codeception\Command\Run), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#25 /app/vendor/symfony/console/Application.php(149): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#26 /app/vendor/codeception/codeception/src/Codeception/Application.php(108): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#27 /app/vendor/codeception/codeception/codecept(43): Codeception\Application->run()
#28 {main}
------------------------------------
RedisPhp72Cest: Test default configuration | "2.3.1"
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72Cest:testDefaultConfiguration
Test: src/Test/Functional/Acceptance/RedisPhp72Cest.php:testDefaultConfiguration
Scenario --
 I cleanup work dir 
 I is cache work dir exists "2.3.1"
 I clone template to work dir "2.3.1"
 I create auth json 
 I create artifacts dir 
 I create artifact current tested code "ece-t...","2002...."
 I add artifacts repo to composer 
 I add dependency to composer "magento/ece-t...","2002.1.99"
 I add ece docker git repo to composer 
 I add cloud components git repo to composer 
 I add cloud patches git repo to composer 
 I add quality patches git repo to composer 
 I get dependency version "magento/magento-cloud-docker"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-components"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-patches"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/quality-patches"
 I add dependency to composer "magento/q...","dev-maste..."
 I assert true true,"Can not add dependency magento/qual..."
 I composer update 
 I assert true true,"Composer update failed"
 I cache work dir "2.3.1"
sh: rsync: not found
 I read services yaml 
 I write services yaml {"mysql":{"type":"mysql:10.2","di...}
 I read app magento yaml 
 I write app magento yaml {"name":"mymagento","type":"ph...}
 I get exposed port 
 I generate docker compose "--mode=production --expose-d..."
 I run docker compose command "run build cloud-build"
 I assert true true,"Build phase was failed"
 I start environment 
 I assert true true,"Docker could not start"
 I run docker compose command "run deploy cloud-deploy"
 I assert true true,"Deploy phase was failed"
 I run docker compose command "run deploy cloud-post-deploy"
 I assert true true,"Post Deploy phase was failed"
 I download from container "/app/e...","/tmp/a...","deploy"
 I assert true true
 I assert same "Cm_Cache_...","Cm_Cache_...","Wrong bac..."
 I assert array subset {"backend_opti...},{"backend":"Cm...}
 I assert same "Cm_Cache_...","Cm_Cache_...","Wrong bac..."
 I assert array subset {"backend_opti...},{"backend":"Cm...}
 I assert array not has key "type",{"frontend":{"default...}
 I am on page "/"
 I see "Home page"
 I see "CMS homepage content goes here."
 I stop environment 
 I remove work dir 
 PASSED 

RedisPhp72Cest: Test default configuration | "2.3.2"
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72Cest:testDefaultConfiguration
Test: src/Test/Functional/Acceptance/RedisPhp72Cest.php:testDefaultConfiguration
Scenario --
 I cleanup work dir 
 I is cache work dir exists "2.3.2"
 I clone template to work dir "2.3.2"
 I create auth json 
 I create artifacts dir 
 I create artifact current tested code "ece-t...","2002...."
 I add artifacts repo to composer 
 I add dependency to composer "magento/ece-t...","2002.1.99"
 I add ece docker git repo to composer 
 I add cloud components git repo to composer 
 I add cloud patches git repo to composer 
 I add quality patches git repo to composer 
 I get dependency version "magento/magento-cloud-docker"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-components"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-patches"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/quality-patches"
 I add dependency to composer "magento/q...","dev-maste..."
 I assert true true,"Can not add dependency magento/qual..."
 I composer update 
 I assert true true,"Composer update failed"
 I cache work dir "2.3.2"
sh: rsync: not found
 I read services yaml 
 I write services yaml {"mysql":{"type":"mysql:10.2","di...}
 I read app magento yaml 
 I write app magento yaml {"name":"mymagento","type":"ph...}
 I get exposed port 
 I generate docker compose "--mode=production --expose-d..."
 I run docker compose command "run build cloud-build"
 I assert true true,"Build phase was failed"
 I start environment 
 I assert true true,"Docker could not start"
 I run docker compose command "run deploy cloud-deploy"
 I assert true true,"Deploy phase was failed"
 I run docker compose command "run deploy cloud-post-deploy"
 I assert true true,"Post Deploy phase was failed"
 I download from container "/app/e...","/tmp/a...","deploy"
 I assert true true
 I assert same "Cm_Cache_...","Cm_Cache_...","Wrong bac..."
 I assert array subset {"backend_opti...},{"backend":"Cm...}
 I assert same "Cm_Cache_...","Cm_Cache_...","Wrong bac..."
 I assert array subset {"backend_opti...},{"backend":"Cm...}
 I assert array not has key "type",{"frontend":{"default...}
 I am on page "/"
 I see "Home page"
 I see "CMS homepage content goes here."
 I stop environment 
 I remove work dir 
 PASSED 

RedisPhp72Cest: Test wrong configuration | false,false,"The REDIS_BACKEND variable contai...","","2.3.0",{"stage":{"deploy":{"REDIS_BACKEND...}
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72Cest:testWrongConfiguration
Test: src/Test/Functional/Acceptance/RedisPhp72Cest.php:testWrongConfiguration
Scenario --
 I cleanup work dir 
 I is cache work dir exists "2.3.0"
 I clone template to work dir "2.3.0"
 I create auth json 
 I create artifacts dir 
 I create artifact current tested code "ece-t...","2002...."
 I add artifacts repo to composer 
 I add dependency to composer "magento/ece-t...","2002.1.99"
 I add ece docker git repo to composer 
 I add cloud components git repo to composer 
 I add cloud patches git repo to composer 
 I add quality patches git repo to composer 
 I get dependency version "magento/magento-cloud-docker"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-components"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-patches"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/quality-patches"
 I add dependency to composer "magento/q...","dev-maste..."
 I assert true true,"Can not add dependency magento/qual..."
 I composer update 
 I assert true true,"Composer update failed"
 I cache work dir "2.3.0"
sh: rsync: not found
 I read services yaml 
 I write services yaml {"mysql":{"type":"mysql:10.2","di...}
 I read app magento yaml 
 I write app magento yaml {"name":"mymagento","type":"ph...}
 I get exposed port 
 I generate docker compose "--mode=production --expose-d..."
 I write env magento yaml {"stage":{"deploy":{"REDIS_BAC...}
 I run docker compose command "run build cloud-build"
 I assert same false,false
 I see in output "The REDIS_BACKEND variable contains an..."
 I run docker compose command "run build cloud-deploy"
 I assert same false,false
 I see in output ""
 I stop environment 
 I remove work dir 
 PASSED 

RedisPhp72Cest: Test wrong configuration | false,false,"The REDIS_BACKEND variable contai...","","2.3.2",{"stage":{"deploy":{"REDIS_BACKEND...}
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72Cest:testWrongConfiguration
Test: src/Test/Functional/Acceptance/RedisPhp72Cest.php:testWrongConfiguration
Scenario --
 I cleanup work dir 
 I is cache work dir exists "2.3.2"
 I clone template to work dir "2.3.2"
 I create auth json 
 I create artifacts dir 
 I create artifact current tested code "ece-t...","2002...."
 I add artifacts repo to composer 
 I add dependency to composer "magento/ece-t...","2002.1.99"
 I add ece docker git repo to composer 
 I add cloud components git repo to composer 
 I add cloud patches git repo to composer 
 I add quality patches git repo to composer 
 I get dependency version "magento/magento-cloud-docker"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-components"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-patches"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/quality-patches"
 I add dependency to composer "magento/q...","dev-maste..."
 I assert true true,"Can not add dependency magento/qual..."
 I composer update 
 I assert true true,"Composer update failed"
 I cache work dir "2.3.2"
sh: rsync: not found
 I read services yaml 
 I write services yaml {"mysql":{"type":"mysql:10.2","di...}
 I read app magento yaml 
 I write app magento yaml {"name":"mymagento","type":"ph...}
 I get exposed port 
 I generate docker compose "--mode=production --expose-d..."
 I write env magento yaml {"stage":{"deploy":{"REDIS_BAC...}
 I run docker compose command "run build cloud-build"
 I assert same false,false
 I see in output "The REDIS_BACKEND variable contains an..."
 I run docker compose command "run build cloud-deploy"
 I assert same false,false
 I see in output ""
 I stop environment 
 I remove work dir 
 PASSED 

------------------------------------------------------------
591x DEPRECATION: Calling the "Symfony\Component\EventDispatcher\EventDispatcherInterface::dispatch()" method with the event name as the first argument is deprecated since Symfony 4.3, pass it as the second argument and provide the event object as the first argument instead. /app/vendor/symfony/event-dispatcher/EventDispatcher.php:58
120x DEPRECATION: Passing a command as string when creating a "Symfony\Component\Process\Process" instance is deprecated since Symfony 4.2, pass it as an array of its arguments instead, or use the "Process::fromShellCommandline()" constructor if you need features provided by the shell. /app/vendor/symfony/process/Process.php:147
60x DEPRECATION: The Robo\Common\ProcessUtils::escapeArgument() method is a copy of a method that was deprecated by Symfony 3.3 and removed in Symfony 4; it will be removed in Robo 2.0. /app/vendor/consolidation/robo/src/Common/ProcessUtils.php:39
8x DEPRECATION: The "Symfony\Component\BrowserKit\Response::getStatus()" method is deprecated since Symfony 4.3, use getStatusCode() instead. /app/vendor/symfony/browser-kit/Response.php:100

Time: 2.06 hours, Memory: 20.00 MB

There was 1 failure:

---------
1) RedisPhp72Cest: Test default configuration | "2.3.0"
 Test  src/Test/Functional/Acceptance/RedisPhp72Cest.php:testDefaultConfiguration
 Step  See "Home page"
 Fail  Failed asserting that  on page /
-->  Warning: Redis::connect(): php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution in /app/vendor/colinmollenhour/credis/Client.php on line 456 Warning: Redis::connect(): php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution in /app/vendor/col
[Content too long to display. See complete response in '/app/tests/functional/_output/' directory]
--> contains "Home page".

Scenario Steps:

 52. $I->removeWorkDir() at src/Test/Functional/Acceptance/AbstractCest.php:45
 51. $I->stopEnvironment() at src/Test/Functional/Acceptance/AbstractCest.php:44
 50. $I->see("Home page") at src/Test/Functional/Acceptance/RedisCest.php:92
 49. $I->amOnPage("/") at src/Test/Functional/Acceptance/RedisCest.php:91
 48. $I->assertArrayNotHasKey("type",{"frontend":{"defa...}) at src/Test/Functional/Acceptance/RedisCest.php:89
 47. $I->assertArraySubset({"backend_o...},{"backend":...}) at src/Test/Functional/Acceptance/RedisCest.php:87

FAILURES!
Tests: 7, Assertions: 85, Failures: 1, Skipped: 1.
run with `-v` to get more info about skipped or incomplete tests
- XML report generated in file:///app/tests/functional/_output/junit.xml

This comment was generated by Jenkins job ece-tools/functional build 53.

magento-cloud-ft-jenkins-svc commented 3 years ago

PHP 7.2 RedisPhp72GoodConfigCest Output

Codeception PHP Testing Framework v2.5.6
Powered by PHPUnit 7.5.20 by Sebastian Bergmann and contributors.
Running with seed: 

Acceptance Tests (9) ---------------------------------------
RedisPhp72GoodConfigCest: Test default configuration
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72GoodConfigCest:testDefaultConfiguration
Test: src/Test/Functional/Acceptance/RedisPhp72GoodConfigCest.php:testDefaultConfiguration
Scenario --
 SKIPPED 
RedisPhp72GoodConfigCest: Test wrong configuration
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72GoodConfigCest:testWrongConfiguration
Test: src/Test/Functional/Acceptance/RedisPhp72GoodConfigCest.php:testWrongConfiguration
Scenario --
 SKIPPED 
RedisPhp72GoodConfigCest: Test good configuration | {"stage":{"deploy":{"REDIS_BA...},"Cm_Cache_Backend_Redis",{"backend_options":{"server":...},"2.3.0"
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72GoodConfigCest:testGoodConfiguration
Test: src/Test/Functional/Acceptance/RedisPhp72GoodConfigCest.php:testGoodConfiguration
Scenario --
 I cleanup work dir 
 I is cache work dir exists "2.3.0"
 I clone template to work dir "2.3.0"
 I create auth json 
 I create artifacts dir 
 I create artifact current tested code "ece-t...","2002...."
 I add artifacts repo to composer 
 I add dependency to composer "magento/ece-t...","2002.1.99"
 I add ece docker git repo to composer 
 I add cloud components git repo to composer 
 I add cloud patches git repo to composer 
 I add quality patches git repo to composer 
 I get dependency version "magento/magento-cloud-docker"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-components"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-patches"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/quality-patches"
 I add dependency to composer "magento/q...","dev-maste..."
 I assert true true,"Can not add dependency magento/qual..."
 I composer update 
 I assert true true,"Composer update failed"
 I cache work dir "2.3.0"
sh: rsync: not found
 I read services yaml 
 I write services yaml {"mysql":{"type":"mysql:10.2","di...}
 I read app magento yaml 
 I write app magento yaml {"name":"mymagento","type":"ph...}
 I get exposed port 
 I generate docker compose "--mode=production --expose-d..."
 I write env magento yaml {"stage":{"deploy":{"REDIS_BAC...}
 I run docker compose command "run build cloud-build"
 I assert true true,"Build phase was failed"
 I start environment 
 I assert true true,"Docker could not start"
 I run docker compose command "run deploy cloud-deploy"
 I assert true true,"Deploy phase was failed"
 I run docker compose command "run deploy cloud-post-deploy"
 I assert true true,"Post Deploy phase was failed"
 I download from container "/app/e...","/tmp/a...","deploy"
 I assert true true
 I assert same "Cm_Cache_...","Cm_Cache_...","Wrong bac..."
 I assert array subset {"backend_opti...},{"backend":"Cm...}
 I am on page "/"
 I see "Home page"
 I see "CMS homepage content goes here."
 I stop environment 
 I remove work dir 
 PASSED 

RedisPhp72GoodConfigCest: Test good configuration | {"stage":{"deploy":{"REDIS...},"\Magento\Framework\Cache\...",{"backend_options":{"serve...},"2.3.0"
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72GoodConfigCest:testGoodConfiguration
Test: src/Test/Functional/Acceptance/RedisPhp72GoodConfigCest.php:testGoodConfiguration
Scenario --
 I cleanup work dir 
 I is cache work dir exists "2.3.0"
 I clone template to work dir "2.3.0"
 I create auth json 
 I create artifacts dir 
 I create artifact current tested code "ece-t...","2002...."
 I add artifacts repo to composer 
 I add dependency to composer "magento/ece-t...","2002.1.99"
 I add ece docker git repo to composer 
 I add cloud components git repo to composer 
 I add cloud patches git repo to composer 
 I add quality patches git repo to composer 
 I get dependency version "magento/magento-cloud-docker"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-components"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-patches"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/quality-patches"
 I add dependency to composer "magento/q...","dev-maste..."
 I assert true true,"Can not add dependency magento/qual..."
 I composer update 
 I assert true true,"Composer update failed"
 I cache work dir "2.3.0"
sh: rsync: not found
 I read services yaml 
 I write services yaml {"mysql":{"type":"mysql:10.2","di...}
 I read app magento yaml 
 I write app magento yaml {"name":"mymagento","type":"ph...}
 I get exposed port 
 I generate docker compose "--mode=production --expose-d..."
 I write env magento yaml {"stage":{"deploy":{"REDIS_BAC...}
 I run docker compose command "run build cloud-build"
 I assert true true,"Build phase was failed"
 I start environment 
 I assert true true,"Docker could not start"
 I run docker compose command "run deploy cloud-deploy"
 I assert true true,"Deploy phase was failed"
 I run docker compose command "run deploy cloud-post-deploy"
 I assert true true,"Post Deploy phase was failed"
 I download from container "/app/e...","/tmp/a...","deploy"
 I assert true true
 I assert same "\Magento\...","\Magento\...","Wrong bac..."
 I assert array subset {"backend_opti...},{"backend":"\\...}
 I am on page "/"
 I see "Home page"
 I see "CMS homepage content goes here."
 I stop environment 
 I remove work dir 
 PASSED 

RedisPhp72GoodConfigCest: Test good configuration | {"stage":{"deploy":{"REDIS...},"\Magento\Framework\Cache\...",{"backend_options":{"remot...},"2.3.0"
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72GoodConfigCest:testGoodConfiguration
Test: src/Test/Functional/Acceptance/RedisPhp72GoodConfigCest.php:testGoodConfiguration
Scenario --
 I cleanup work dir 
 I is cache work dir exists "2.3.0"
 I clone template to work dir "2.3.0"
 I create auth json 
 I create artifacts dir 
 I create artifact current tested code "ece-t...","2002...."
 I add artifacts repo to composer 
 I add dependency to composer "magento/ece-t...","2002.1.99"
 I add ece docker git repo to composer 
 I add cloud components git repo to composer 
 I add cloud patches git repo to composer 
 I add quality patches git repo to composer 
 I get dependency version "magento/magento-cloud-docker"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-components"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-patches"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/quality-patches"
 I add dependency to composer "magento/q...","dev-maste..."
 I assert true true,"Can not add dependency magento/qual..."
 I composer update 
 I assert true true,"Composer update failed"
 I cache work dir "2.3.0"
sh: rsync: not found
 I read services yaml 
 I write services yaml {"mysql":{"type":"mysql:10.2","di...}
 I read app magento yaml 
 I write app magento yaml {"name":"mymagento","type":"ph...}
 I get exposed port 
 I generate docker compose "--mode=production --expose-d..."
 I write env magento yaml {"stage":{"deploy":{"REDIS_BAC...}
 I run docker compose command "run build cloud-build"
 I assert true true,"Build phase was failed"
 I start environment 
 I assert true true,"Docker could not start"
 I run docker compose command "run deploy cloud-deploy"
 I assert true true,"Deploy phase was failed"
 I run docker compose command "run deploy cloud-post-deploy"
 I assert true true,"Post Deploy phase was failed"
 I download from container "/app/e...","/tmp/a...","deploy"
 I assert true true
 I assert same "\Magento\...","\Magento\...","Wrong bac..."
 I assert array subset {"backend_opti...},{"backend":"\\...}
 I am on page "/"
 I see "Home page"
 I stop environment 
 I remove work dir 
 FAIL 

------------------------------------
Message: Failed asserting that  on page /
-->  Warning: Redis::connect(): php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution in /app/vendor/colinmollenhour/credis/Client.php on line 456 Warning: Redis::connect(): php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution in /app/vendor/col
[Content too long to display. See complete response in '/app/tests/functional/_output/' directory]
--> contains "Home page".
------------------------------------
Stack Trace: 
#0 /app/vendor/phpunit/phpunit/src/Framework/Constraint/Constraint.php(60): PHPUnit\Framework\Constraint\Constraint->fail(' Warning: Redis...', '')
#1 /app/vendor/phpunit/phpunit/src/Framework/Assert.php(2307): PHPUnit\Framework\Constraint\Constraint->evaluate(' Warning: Redis...', '')
#2 /app/vendor/codeception/codeception/src/Codeception/Util/Shared/Asserts.php(311): PHPUnit\Framework\Assert::assertThat(' Warning: Redis...', Object(Codeception\PHPUnit\Constraint\Page), '')
#3 /app/vendor/codeception/codeception/src/Codeception/Lib/InnerBrowser.php(1704): Codeception\Module->assertThat(' Warning: Redis...', Object(Codeception\PHPUnit\Constraint\Page), '')
#4 /app/vendor/codeception/codeception/src/Codeception/Lib/InnerBrowser.php(480): Codeception\Lib\InnerBrowser->assertPageContains('Home page')
#5 [internal function]: Codeception\Lib\InnerBrowser->see('Home page')
#6 /app/vendor/codeception/codeception/src/Codeception/Step.php(265): call_user_func_array(Array, Array)
#7 /app/vendor/codeception/codeception/src/Codeception/Scenario.php(72): Codeception\Step->run(Object(Codeception\Lib\ModuleContainer))
#8 /app/vendor/magento/magento-cloud-docker/tests/functional/_support/_generated/CliTesterActions.php(1538): Codeception\Scenario->runStep(Object(Codeception\Step\Assertion))
#9 /app/src/Test/Functional/Acceptance/RedisCest.php(191): CliTester->see('Home page')
#10 [internal function]: Magento\MagentoCloud\Test\Functional\Acceptance\RedisCest->testGoodConfiguration(Object(CliTester), Object(Codeception\Example))
#11 /app/vendor/codeception/codeception/src/Codeception/Lib/Di.php(127): ReflectionMethod->invokeArgs(Object(Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72GoodConfigCest), Array)
#12 /app/vendor/codeception/codeception/src/Codeception/Test/Cest.php(138): Codeception\Lib\Di->injectDependencies(Object(Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72GoodConfigCest), 'testGoodConfigu...', Array)
#13 /app/vendor/codeception/codeception/src/Codeception/Test/Cest.php(147): Codeception\Test\Cest->invoke('testGoodConfigu...', Array)
#14 /app/vendor/codeception/codeception/src/Codeception/Test/Cest.php(82): Codeception\Test\Cest->executeTestMethod(Object(CliTester))
#15 /app/vendor/codeception/codeception/src/Codeception/Test/Test.php(89): Codeception\Test\Cest->test()
#16 /app/vendor/phpunit/phpunit/src/Framework/TestSuite.php(746): Codeception\Test\Test->run(Object(PHPUnit\Framework\TestResult))
#17 /app/vendor/codeception/phpunit-wrapper/src/Runner.php(118): PHPUnit\Framework\TestSuite->run(Object(PHPUnit\Framework\TestResult))
#18 /app/vendor/codeception/codeception/src/Codeception/SuiteManager.php(158): Codeception\PHPUnit\Runner->doEnhancedRun(Object(Codeception\Suite), Object(PHPUnit\Framework\TestResult), Array)
#19 /app/vendor/codeception/codeception/src/Codeception/Codecept.php(192): Codeception\SuiteManager->run(Object(Codeception\PHPUnit\Runner), Object(PHPUnit\Framework\TestResult), Array)
#20 /app/vendor/codeception/codeception/src/Codeception/Codecept.php(159): Codeception\Codecept->runSuite(Array, 'Acceptance', 'RedisPhp72GoodC...')
#21 /app/vendor/codeception/codeception/src/Codeception/Command/Run.php(384): Codeception\Codecept->run('Acceptance', 'RedisPhp72GoodC...', Array)
#22 /app/vendor/symfony/console/Command/Command.php(255): Codeception\Command\Run->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#23 /app/vendor/symfony/console/Application.php(1009): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#24 /app/vendor/symfony/console/Application.php(273): Symfony\Component\Console\Application->doRunCommand(Object(Codeception\Command\Run), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#25 /app/vendor/symfony/console/Application.php(149): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#26 /app/vendor/codeception/codeception/src/Codeception/Application.php(108): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#27 /app/vendor/codeception/codeception/codecept(43): Codeception\Application->run()
#28 {main}
------------------------------------
RedisPhp72GoodConfigCest: Test good configuration | {"stage":{"deploy":{"REDIS...},"\Magento\Framework\Cache\...",{"backend_options":{"serve...},"2.3.1"
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72GoodConfigCest:testGoodConfiguration
Test: src/Test/Functional/Acceptance/RedisPhp72GoodConfigCest.php:testGoodConfiguration
Scenario --
 I cleanup work dir 
 I is cache work dir exists "2.3.1"
 I clone template to work dir "2.3.1"
 I create auth json 
 I create artifacts dir 
 I create artifact current tested code "ece-t...","2002...."
 I add artifacts repo to composer 
 I add dependency to composer "magento/ece-t...","2002.1.99"
 I add ece docker git repo to composer 
 I add cloud components git repo to composer 
 I add cloud patches git repo to composer 
 I add quality patches git repo to composer 
 I get dependency version "magento/magento-cloud-docker"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-components"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-patches"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/quality-patches"
 I add dependency to composer "magento/q...","dev-maste..."
 I assert true true,"Can not add dependency magento/qual..."
 I composer update 
 I assert true true,"Composer update failed"
 I cache work dir "2.3.1"
sh: rsync: not found
 I read services yaml 
 I write services yaml {"mysql":{"type":"mysql:10.2","di...}
 I read app magento yaml 
 I write app magento yaml {"name":"mymagento","type":"ph...}
 I get exposed port 
 I generate docker compose "--mode=production --expose-d..."
 I write env magento yaml {"stage":{"deploy":{"REDIS_BAC...}
 I run docker compose command "run build cloud-build"
 I assert true true,"Build phase was failed"
 I start environment 
 I assert true true,"Docker could not start"
 I run docker compose command "run deploy cloud-deploy"
 I assert true true,"Deploy phase was failed"
 I run docker compose command "run deploy cloud-post-deploy"
 I assert true true,"Post Deploy phase was failed"
 I download from container "/app/e...","/tmp/a...","deploy"
 I assert true true
 I assert same "\Magento\...","\Magento\...","Wrong bac..."
 I assert array subset {"backend_opti...},{"backend":"\\...}
 I am on page "/"
 I see "Home page"
 I see "CMS homepage content goes here."
 I stop environment 
 I remove work dir 
 PASSED 

RedisPhp72GoodConfigCest: Test good configuration | {"stage":{"deploy":{"REDIS...},"\Magento\Framework\Cache\...",{"backend_options":{"remot...},"2.3.1"
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72GoodConfigCest:testGoodConfiguration
Test: src/Test/Functional/Acceptance/RedisPhp72GoodConfigCest.php:testGoodConfiguration
Scenario --
 I cleanup work dir 
 I is cache work dir exists "2.3.1"
 I clone template to work dir "2.3.1"
 I create auth json 
 I create artifacts dir 
 I create artifact current tested code "ece-t...","2002...."
 I add artifacts repo to composer 
 I add dependency to composer "magento/ece-t...","2002.1.99"
 I add ece docker git repo to composer 
 I add cloud components git repo to composer 
 I add cloud patches git repo to composer 
 I add quality patches git repo to composer 
 I get dependency version "magento/magento-cloud-docker"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-components"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-patches"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/quality-patches"
 I add dependency to composer "magento/q...","dev-maste..."
 I assert true true,"Can not add dependency magento/qual..."
 I composer update 
 I assert true true,"Composer update failed"
 I cache work dir "2.3.1"
sh: rsync: not found
 I read services yaml 
 I write services yaml {"mysql":{"type":"mysql:10.2","di...}
 I read app magento yaml 
 I write app magento yaml {"name":"mymagento","type":"ph...}
 I get exposed port 
 I generate docker compose "--mode=production --expose-d..."
 I write env magento yaml {"stage":{"deploy":{"REDIS_BAC...}
 I run docker compose command "run build cloud-build"
 I assert true true,"Build phase was failed"
 I start environment 
 I assert true true,"Docker could not start"
 I run docker compose command "run deploy cloud-deploy"
 I assert true true,"Deploy phase was failed"
 I run docker compose command "run deploy cloud-post-deploy"
 I assert true true,"Post Deploy phase was failed"
 I download from container "/app/e...","/tmp/a...","deploy"
 I assert true true
 I assert same "\Magento\...","\Magento\...","Wrong bac..."
 I assert array subset {"backend_opti...},{"backend":"\\...}
 I am on page "/"
 I see "Home page"
 I see "CMS homepage content goes here."
 I stop environment 
 I remove work dir 
 PASSED 

RedisPhp72GoodConfigCest: Test good configuration | {"stage":{"deploy":{"REDIS...},"\Magento\Framework\Cache\...",{"backend_options":{"serve...},"2.3.2"
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72GoodConfigCest:testGoodConfiguration
Test: src/Test/Functional/Acceptance/RedisPhp72GoodConfigCest.php:testGoodConfiguration
Scenario --
 I cleanup work dir 
 I is cache work dir exists "2.3.2"
 I clone template to work dir "2.3.2"
 I create auth json 
 I create artifacts dir 
 I create artifact current tested code "ece-t...","2002...."
 I add artifacts repo to composer 
 I add dependency to composer "magento/ece-t...","2002.1.99"
 I add ece docker git repo to composer 
 I add cloud components git repo to composer 
 I add cloud patches git repo to composer 
 I add quality patches git repo to composer 
 I get dependency version "magento/magento-cloud-docker"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-components"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-patches"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/quality-patches"
 I add dependency to composer "magento/q...","dev-maste..."
 I assert true true,"Can not add dependency magento/qual..."
 I composer update 
 I assert true true,"Composer update failed"
 I cache work dir "2.3.2"
sh: rsync: not found
 I read services yaml 
 I write services yaml {"mysql":{"type":"mysql:10.2","di...}
 I read app magento yaml 
 I write app magento yaml {"name":"mymagento","type":"ph...}
 I get exposed port 
 I generate docker compose "--mode=production --expose-d..."
 I write env magento yaml {"stage":{"deploy":{"REDIS_BAC...}
 I run docker compose command "run build cloud-build"
 I assert true true,"Build phase was failed"
 I start environment 
 I assert true true,"Docker could not start"
 I run docker compose command "run deploy cloud-deploy"
 I assert true true,"Deploy phase was failed"
 I run docker compose command "run deploy cloud-post-deploy"
 I assert true true,"Post Deploy phase was failed"
 I download from container "/app/e...","/tmp/a...","deploy"
 I assert true true
 I assert same "\Magento\...","\Magento\...","Wrong bac..."
 I assert array subset {"backend_opti...},{"backend":"\\...}
 I am on page "/"
 I see "Home page"
 I see "CMS homepage content goes here."
 I stop environment 
 I remove work dir 
 PASSED 

RedisPhp72GoodConfigCest: Test good configuration | {"stage":{"deploy":{"REDIS...},"\Magento\Framework\Cache\...",{"backend_options":{"remot...},"2.3.2"
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\RedisPhp72GoodConfigCest:testGoodConfiguration
Test: src/Test/Functional/Acceptance/RedisPhp72GoodConfigCest.php:testGoodConfiguration
Scenario --
 I cleanup work dir 
 I is cache work dir exists "2.3.2"
 I clone template to work dir "2.3.2"
 I create auth json 
 I create artifacts dir 
 I create artifact current tested code "ece-t...","2002...."
 I add artifacts repo to composer 
 I add dependency to composer "magento/ece-t...","2002.1.99"
 I add ece docker git repo to composer 
 I add cloud components git repo to composer 
 I add cloud patches git repo to composer 
 I add quality patches git repo to composer 
 I get dependency version "magento/magento-cloud-docker"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-components"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-patches"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/quality-patches"
 I add dependency to composer "magento/q...","dev-maste..."
 I assert true true,"Can not add dependency magento/qual..."
 I composer update 
 I assert true true,"Composer update failed"
 I cache work dir "2.3.2"
sh: rsync: not found
 I read services yaml 
 I write services yaml {"mysql":{"type":"mysql:10.2","di...}
 I read app magento yaml 
 I write app magento yaml {"name":"mymagento","type":"ph...}
 I get exposed port 
 I generate docker compose "--mode=production --expose-d..."
 I write env magento yaml {"stage":{"deploy":{"REDIS_BAC...}
 I run docker compose command "run build cloud-build"
 I assert true true,"Build phase was failed"
 I start environment 
 I assert true true,"Docker could not start"
 I run docker compose command "run deploy cloud-deploy"
 I assert true true,"Deploy phase was failed"
 I run docker compose command "run deploy cloud-post-deploy"
 I assert true true,"Post Deploy phase was failed"
 I download from container "/app/e...","/tmp/a...","deploy"
 I assert true true
 I assert same "\Magento\...","\Magento\...","Wrong bac..."
 I assert array subset {"backend_opti...},{"backend":"\\...}
 I am on page "/"
 I see "Home page"
 I see "CMS homepage content goes here."
 I stop environment 
 I remove work dir 
 PASSED 

------------------------------------------------------------
713x DEPRECATION: Calling the "Symfony\Component\EventDispatcher\EventDispatcherInterface::dispatch()" method with the event name as the first argument is deprecated since Symfony 4.3, pass it as the second argument and provide the event object as the first argument instead. /app/vendor/symfony/event-dispatcher/EventDispatcher.php:58
148x DEPRECATION: Passing a command as string when creating a "Symfony\Component\Process\Process" instance is deprecated since Symfony 4.2, pass it as an array of its arguments instead, or use the "Process::fromShellCommandline()" constructor if you need features provided by the shell. /app/vendor/symfony/process/Process.php:147
71x DEPRECATION: The Robo\Common\ProcessUtils::escapeArgument() method is a copy of a method that was deprecated by Symfony 3.3 and removed in Symfony 4; it will be removed in Robo 2.0. /app/vendor/consolidation/robo/src/Common/ProcessUtils.php:39
14x DEPRECATION: The "Symfony\Component\BrowserKit\Response::getStatus()" method is deprecated since Symfony 4.3, use getStatusCode() instead. /app/vendor/symfony/browser-kit/Response.php:100

Time: 2.11 hours, Memory: 20.00 MB

There was 1 failure:

---------
1) RedisPhp72GoodConfigCest: Test good configuration | {"stage":{"deploy":{"REDIS...},"\Magento\Framework\Cache\...",{"backend_options":{"remot...},"2.3.0"
 Test  src/Test/Functional/Acceptance/RedisPhp72GoodConfigCest.php:testGoodConfiguration
 Step  See "Home page"
 Fail  Failed asserting that  on page /
-->  Warning: Redis::connect(): php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution in /app/vendor/colinmollenhour/credis/Client.php on line 456 Warning: Redis::connect(): php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution in /app/vendor/col
[Content too long to display. See complete response in '/app/tests/functional/_output/' directory]
--> contains "Home page".

Scenario Steps:

 50. $I->removeWorkDir() at src/Test/Functional/Acceptance/AbstractCest.php:45
 49. $I->stopEnvironment() at src/Test/Functional/Acceptance/AbstractCest.php:44
 48. $I->see("Home page") at src/Test/Functional/Acceptance/RedisCest.php:191
 47. $I->amOnPage("/") at src/Test/Functional/Acceptance/RedisCest.php:190
 46. $I->assertArraySubset({"backend_o...},{"backend":...}) at src/Test/Functional/Acceptance/RedisCest.php:187
 45. $I->assertSame("\Magent...","\Magent...","Wrong b...") at src/Test/Functional/Acceptance/RedisCest.php:182

FAILURES!
Tests: 9, Assertions: 97, Failures: 1, Skipped: 2.
run with `-v` to get more info about skipped or incomplete tests
- XML report generated in file:///app/tests/functional/_output/junit.xml

This comment was generated by Jenkins job ece-tools/functional build 53.

magento-cloud-ft-jenkins-svc commented 3 years ago

PHP 7.4 AcceptanceCeCest Output

Codeception PHP Testing Framework v2.5.6
Powered by PHPUnit 7.5.20 by Sebastian Bergmann and contributors.
Running with seed: 

Acceptance Tests (1) ---------------------------------------
AcceptanceCeCest: Test with split build command
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\AcceptanceCeCest:testWithSplitBuildCommand
Test: src/Test/Functional/Acceptance/AcceptanceCeCest.php:testWithSplitBuildCommand
Scenario --
 I cleanup work dir 
 I is cache work dir exists "master"
 I clone template to work dir "master"
 I create auth json 
 I create artifacts dir 
 I create artifact current tested code "ece-t...","2002...."
 I add artifacts repo to composer 
 I add dependency to composer "magento/ece-t...","2002.1.99"
 I add ece docker git repo to composer 
 I add cloud components git repo to composer 
 I add cloud patches git repo to composer 
 I add quality patches git repo to composer 
 I get dependency version "magento/magento-cloud-docker"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-components"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-patches"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/quality-patches"
 I add dependency to composer "magento/q...","dev-maste..."
 I assert true true,"Can not add dependency magento/qual..."
 I remove dependency from composer "magento/magento-clou..."
 I add dependency to composer "magento/product...","@stable"
 I composer update 
 I generate docker compose "--mode=production"
 I start environment 
 I run docker compose command "run build cloud-build"
 I run docker compose command "run deploy cloud-deploy"
 I am on page "/"

This comment was generated by Jenkins job ece-tools/functional build 53.

magento-cloud-ft-jenkins-svc commented 3 years ago

Unit & Integration Test Results

:x:  One or more unit or integration tests have failed.

Unit Test Output

> phpunit --configuration tests/unit '--log-junit' 'tests/unit/tmp/junit.xml' '--coverage-clover' 'tests/unit/tmp/clover.xml'
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.

.............................................................   61 / 1513 (  4%)
.............................................................  122 / 1513 (  8%)
.............................................................  183 / 1513 ( 12%)
.............................................................  244 / 1513 ( 16%)
.............................................................  305 / 1513 ( 20%)
.............................................................  366 / 1513 ( 24%)
.............................................................  427 / 1513 ( 28%)
.............................................................  488 / 1513 ( 32%)
.FFFF.FF.....................................................  549 / 1513 ( 36%)
.............................................................  610 / 1513 ( 40%)
.............................................................  671 / 1513 ( 44%)
.............................................................  732 / 1513 ( 48%)
.............................................................  793 / 1513 ( 52%)
.............................................................  854 / 1513 ( 56%)
.............................................................  915 / 1513 ( 60%)
.............................................................  976 / 1513 ( 64%)
............................................................. 1037 / 1513 ( 68%)
............................................................. 1098 / 1513 ( 72%)
............................................................. 1159 / 1513 ( 76%)
............................................................. 1220 / 1513 ( 80%)
............................................................. 1281 / 1513 ( 84%)
............................................................. 1342 / 1513 ( 88%)
............................................................. 1403 / 1513 ( 92%)
............................................................. 1464 / 1513 ( 96%)
.................................................             1513 / 1513 (100%)

Time: 17.2 seconds, Memory: 84.50 MB

There were 6 failures:

1) Magento\MagentoCloud\Test\Unit\Config\Validator\Build\ComposerFileTest::testValidateCorrectComposerJson
Expectation failed for method name is equal to 'isGreaterOrEqual' when invoked at least once
Parameter 0 for invocation Magento\MagentoCloud\Package\MagentoVersion::isGreaterOrEqual('2.4.3'): bool does not match expected value.
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'2.3'
+'2.4.3'

/var/jenkins/workspace/ece-tools/unit/src/Config/Validator/Build/ComposerFile.php:87
/var/jenkins/workspace/ece-tools/unit/src/Test/Unit/Config/Validator/Build/ComposerFileTest.php:85

2) Magento\MagentoCloud\Test\Unit\Config\Validator\Build\ComposerFileTest::testValidateCorrectLaminasComposerJson
Expectation failed for method name is equal to 'isGreaterOrEqual' when invoked at least once
Parameter 0 for invocation Magento\MagentoCloud\Package\MagentoVersion::isGreaterOrEqual('2.4.3'): bool does not match expected value.
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'2.3'
+'2.4.3'

/var/jenkins/workspace/ece-tools/unit/src/Config/Validator/Build/ComposerFile.php:87
/var/jenkins/workspace/ece-tools/unit/src/Test/Unit/Config/Validator/Build/ComposerFileTest.php:103

3) Magento\MagentoCloud\Test\Unit\Config\Validator\Build\ComposerFileTest::testValidateCorrectAutoload243ComposerJson
Expectation failed for method name is equal to 'isGreaterOrEqual' when invoked at least once
Parameter 0 for invocation Magento\MagentoCloud\Package\MagentoVersion::isGreaterOrEqual('2.4.3'): bool does not match expected value.
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'2.3'
+'2.4.3'

/var/jenkins/workspace/ece-tools/unit/src/Config/Validator/Build/ComposerFile.php:87
/var/jenkins/workspace/ece-tools/unit/src/Test/Unit/Config/Validator/Build/ComposerFileTest.php:121

4) Magento\MagentoCloud\Test\Unit\Config\Validator\Build\ComposerFileTest::testValidateWrongComposerJson
Expectation failed for method name is equal to 'isGreaterOrEqual' when invoked at least once
Parameter 0 for invocation Magento\MagentoCloud\Package\MagentoVersion::isGreaterOrEqual('2.4.3'): bool does not match expected value.
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'2.3'
+'2.4.3'

/var/jenkins/workspace/ece-tools/unit/src/Config/Validator/Build/ComposerFile.php:87
/var/jenkins/workspace/ece-tools/unit/src/Test/Unit/Config/Validator/Build/ComposerFileTest.php:150

5) Magento\MagentoCloud\Test\Unit\Config\Validator\Build\ComposerFileTest::testValidateMagentoHigherEqual243
Expectation failed for method name is equal to 'isGreaterOrEqual' when invoked at least once
Parameter 0 for invocation Magento\MagentoCloud\Package\MagentoVersion::isGreaterOrEqual('2.3'): bool does not match expected value.
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'2.4.3'
+'2.3'

/var/jenkins/workspace/ece-tools/unit/src/Config/Validator/Build/ComposerFile.php:87
/var/jenkins/workspace/ece-tools/unit/src/Test/Unit/Config/Validator/Build/ComposerFileTest.php:184

6) Magento\MagentoCloud\Test\Unit\Config\Validator\Build\ComposerFileTest::testValidateComposerFileNotExists
Expectation failed for method name is equal to 'isGreaterOrEqual' when invoked at least once
Parameter 0 for invocation Magento\MagentoCloud\Package\MagentoVersion::isGreaterOrEqual('2.4.3'): bool does not match expected value.
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'2.3'
+'2.4.3'

/var/jenkins/workspace/ece-tools/unit/src/Config/Validator/Build/ComposerFile.php:87
/var/jenkins/workspace/ece-tools/unit/src/Test/Unit/Config/Validator/Build/ComposerFileTest.php:207

FAILURES!
Tests: 1513, Assertions: 4743, Failures: 6.

Generating code coverage report in Clover XML format ... done
Script phpunit --configuration tests/unit handling the test:unit event returned with error code 1

Integration Test Output

> phpunit --configuration tests/integration '--log-junit' 'tests/integration/tmp/junit.xml'
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.

................................................................. 65 / 65 (100%)

Time: 3.79 seconds, Memory: 28.00 MB

OK (65 tests, 69 assertions)

This comment was generated by Jenkins job ece-tools/unit build 33.

magento-cloud-ft-jenkins-svc commented 3 years ago

Static Analysis & Code Style Results

:white_check_mark:  All static analysis and code style checks have passed.

PHP Codesniffer Output

> phpcs src --standard=tests/static/phpcs-ruleset.xml -p -n
............................................................  60 / 702 (9%)
............................................................ 120 / 702 (17%)
............................................................ 180 / 702 (26%)
............................................................ 240 / 702 (34%)
............................................................ 300 / 702 (43%)
............................................................ 360 / 702 (51%)
............................................................ 420 / 702 (60%)
............................................................ 480 / 702 (68%)
............................................................ 540 / 702 (77%)
............................................................ 600 / 702 (85%)
............................................................ 660 / 702 (94%)
..........................................                   702 / 702 (100%)

Time: 24.93 secs; Memory: 24MB

PHP Mess Detector Output


Found 0 violations and 0 errors in 16548ms

No mess detected

PHPStan Output

> phpstan analyse -c tests/static/phpstan.neon '--no-progress'

 [OK] No errors                                                                 

This comment was generated by Jenkins job ece-tools/static build 32.

magento-cloud-ft-jenkins-svc commented 3 years ago

Unit & Integration Test Results

:x:  One or more unit or integration tests have failed.

Unit Test Output

> phpunit --configuration tests/unit '--log-junit' 'tests/unit/tmp/junit.xml' '--coverage-clover' 'tests/unit/tmp/clover.xml'
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.

.............................................................   61 / 1513 (  4%)
.............................................................  122 / 1513 (  8%)
.............................................................  183 / 1513 ( 12%)
.............................................................  244 / 1513 ( 16%)
.............................................................  305 / 1513 ( 20%)
.............................................................  366 / 1513 ( 24%)
.............................................................  427 / 1513 ( 28%)
.............................................................  488 / 1513 ( 32%)
.FFFFFFF.....................................................  549 / 1513 ( 36%)
.............................................................  610 / 1513 ( 40%)
.............................................................  671 / 1513 ( 44%)
.............................................................  732 / 1513 ( 48%)
.............................................................  793 / 1513 ( 52%)
.............................................................  854 / 1513 ( 56%)
.............................................................  915 / 1513 ( 60%)
.............................................................  976 / 1513 ( 64%)
............................................................. 1037 / 1513 ( 68%)
............................................................. 1098 / 1513 ( 72%)
............................................................. 1159 / 1513 ( 76%)
............................................................. 1220 / 1513 ( 80%)
............................................................. 1281 / 1513 ( 84%)
............................................................. 1342 / 1513 ( 88%)
............................................................. 1403 / 1513 ( 92%)
............................................................. 1464 / 1513 ( 96%)
.................................................             1513 / 1513 (100%)

Time: 17.64 seconds, Memory: 84.50 MB

There were 7 failures:

1) Magento\MagentoCloud\Test\Unit\Config\Validator\Build\ComposerFileTest::testValidateCorrectComposerJson
Expectation failed for method name is equal to 'isGreaterOrEqual' when invoked 1 time(s)
Parameter 0 for invocation Magento\MagentoCloud\Package\MagentoVersion::isGreaterOrEqual('2.3'): bool does not match expected value.
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'2.4.3'
+'2.3'

/var/jenkins/workspace/ece-tools/unit/src/Config/Validator/Build/ComposerFile.php:87
/var/jenkins/workspace/ece-tools/unit/src/Test/Unit/Config/Validator/Build/ComposerFileTest.php:89

2) Magento\MagentoCloud\Test\Unit\Config\Validator\Build\ComposerFileTest::testValidateCorrectLaminasComposerJson
Expectation failed for method name is equal to 'isGreaterOrEqual' when invoked 1 time(s)
Parameter 0 for invocation Magento\MagentoCloud\Package\MagentoVersion::isGreaterOrEqual('2.3'): bool does not match expected value.
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'2.4.3'
+'2.3'

/var/jenkins/workspace/ece-tools/unit/src/Config/Validator/Build/ComposerFile.php:87
/var/jenkins/workspace/ece-tools/unit/src/Test/Unit/Config/Validator/Build/ComposerFileTest.php:111

3) Magento\MagentoCloud\Test\Unit\Config\Validator\Build\ComposerFileTest::testValidateCorrectAutoload243ComposerJson
Expectation failed for method name is equal to 'isGreaterOrEqual' when invoked 1 time(s)
Parameter 0 for invocation Magento\MagentoCloud\Package\MagentoVersion::isGreaterOrEqual('2.3'): bool does not match expected value.
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'2.4.3'
+'2.3'

/var/jenkins/workspace/ece-tools/unit/src/Config/Validator/Build/ComposerFile.php:87
/var/jenkins/workspace/ece-tools/unit/src/Test/Unit/Config/Validator/Build/ComposerFileTest.php:133

4) Magento\MagentoCloud\Test\Unit\Config\Validator\Build\ComposerFileTest::testValidateWrongComposerJson
Expectation failed for method name is equal to 'isGreaterOrEqual' when invoked 1 time(s)
Parameter 0 for invocation Magento\MagentoCloud\Package\MagentoVersion::isGreaterOrEqual('2.3'): bool does not match expected value.
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'2.4.3'
+'2.3'

/var/jenkins/workspace/ece-tools/unit/src/Config/Validator/Build/ComposerFile.php:87
/var/jenkins/workspace/ece-tools/unit/src/Test/Unit/Config/Validator/Build/ComposerFileTest.php:166

5) Magento\MagentoCloud\Test\Unit\Config\Validator\Build\ComposerFileTest::testValidateMagentoLower23
Expectation failed for method name is equal to 'isGreaterOrEqual' when invoked 1 time(s)
Parameter 0 for invocation Magento\MagentoCloud\Package\MagentoVersion::isGreaterOrEqual('2.3'): bool does not match expected value.
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'2.4.3'
+'2.3'

/var/jenkins/workspace/ece-tools/unit/src/Config/Validator/Build/ComposerFile.php:87
/var/jenkins/workspace/ece-tools/unit/src/Test/Unit/Config/Validator/Build/ComposerFileTest.php:187

6) Magento\MagentoCloud\Test\Unit\Config\Validator\Build\ComposerFileTest::testValidateMagentoHigherEqual243
Expectation failed for method name is equal to 'isGreaterOrEqual' when invoked 1 time(s)
Parameter 0 for invocation Magento\MagentoCloud\Package\MagentoVersion::isGreaterOrEqual('2.3'): bool does not match expected value.
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'2.4.3'
+'2.3'

/var/jenkins/workspace/ece-tools/unit/src/Config/Validator/Build/ComposerFile.php:87
/var/jenkins/workspace/ece-tools/unit/src/Test/Unit/Config/Validator/Build/ComposerFileTest.php:208

7) Magento\MagentoCloud\Test\Unit\Config\Validator\Build\ComposerFileTest::testValidateComposerFileNotExists
Expectation failed for method name is equal to 'isGreaterOrEqual' when invoked 1 time(s)
Parameter 0 for invocation Magento\MagentoCloud\Package\MagentoVersion::isGreaterOrEqual('2.3'): bool does not match expected value.
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'2.4.3'
+'2.3'

/var/jenkins/workspace/ece-tools/unit/src/Config/Validator/Build/ComposerFile.php:87
/var/jenkins/workspace/ece-tools/unit/src/Test/Unit/Config/Validator/Build/ComposerFileTest.php:235

FAILURES!
Tests: 1513, Assertions: 4740, Failures: 7.

Generating code coverage report in Clover XML format ... done
Script phpunit --configuration tests/unit handling the test:unit event returned with error code 1

Integration Test Output

> phpunit --configuration tests/integration '--log-junit' 'tests/integration/tmp/junit.xml'
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.

................................................................. 65 / 65 (100%)

Time: 3.93 seconds, Memory: 28.00 MB

OK (65 tests, 69 assertions)

This comment was generated by Jenkins job ece-tools/unit build 34.

magento-cloud-ft-jenkins-svc commented 3 years ago

Static Analysis & Code Style Results

:white_check_mark:  All static analysis and code style checks have passed.

PHP Codesniffer Output

> phpcs src --standard=tests/static/phpcs-ruleset.xml -p -n
............................................................  60 / 702 (9%)
............................................................ 120 / 702 (17%)
............................................................ 180 / 702 (26%)
............................................................ 240 / 702 (34%)
............................................................ 300 / 702 (43%)
............................................................ 360 / 702 (51%)
............................................................ 420 / 702 (60%)
............................................................ 480 / 702 (68%)
............................................................ 540 / 702 (77%)
............................................................ 600 / 702 (85%)
............................................................ 660 / 702 (94%)
..........................................                   702 / 702 (100%)

Time: 25.76 secs; Memory: 24MB

PHP Mess Detector Output


Found 0 violations and 0 errors in 17245ms

No mess detected

PHPStan Output

> phpstan analyse -c tests/static/phpstan.neon '--no-progress'

 [OK] No errors                                                                 

This comment was generated by Jenkins job ece-tools/static build 33.

magento-cloud-ft-jenkins-svc commented 3 years ago

Functional Acceptance Test Results

:x:  One or more functional acceptance tests have failed.

PHP 7.1

PHP 7.2

PHP 7.3

PHP 7.4

Output for failed tests is below. If many tests have failed only the first 5 will be included. If you need additional information please reach out to the Magento Cloud team for more details.

This comment was generated by Jenkins job ece-tools/functional build 54.

magento-cloud-ft-jenkins-svc commented 3 years ago

PHP 7.4 AcceptanceCeCest Output

Codeception PHP Testing Framework v2.5.6
Powered by PHPUnit 7.5.20 by Sebastian Bergmann and contributors.
Running with seed: 

Acceptance Tests (1) ---------------------------------------
AcceptanceCeCest: Test with split build command
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\AcceptanceCeCest:testWithSplitBuildCommand
Test: src/Test/Functional/Acceptance/AcceptanceCeCest.php:testWithSplitBuildCommand
Scenario --
 I cleanup work dir 
 I is cache work dir exists "master"
 I clone template to work dir "master"
 I create auth json 
 I create artifacts dir 
 I create artifact current tested code "ece-t...","2002...."
 I add artifacts repo to composer 
 I add dependency to composer "magento/ece-t...","2002.1.99"
 I add ece docker git repo to composer 
 I add cloud components git repo to composer 
 I add cloud patches git repo to composer 
 I add quality patches git repo to composer 
 I get dependency version "magento/magento-cloud-docker"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-components"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-patches"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/quality-patches"
 I add dependency to composer "magento/q...","dev-maste..."
 I assert true true,"Can not add dependency magento/qual..."
 I remove dependency from composer "magento/magento-clou..."
 I add dependency to composer "magento/product...","@stable"
 I composer update 
 I generate docker compose "--mode=production"
 I start environment 
 I run docker compose command "run build cloud-build"
 I run docker compose command "run deploy cloud-deploy"
 I am on page "/"

This comment was generated by Jenkins job ece-tools/functional build 54.

magento-cloud-ft-jenkins-svc commented 3 years ago

Functional Acceptance Test Results

:x:  One or more functional acceptance tests have failed.

PHP 7.1

PHP 7.2

PHP 7.3

PHP 7.4

Output for failed tests is below. If many tests have failed only the first 5 will be included. If you need additional information please reach out to the Magento Cloud team for more details.

This comment was generated by Jenkins job ece-tools/functional build 55.

magento-cloud-ft-jenkins-svc commented 3 years ago

PHP 7.4 AcceptanceCeCest Output

Codeception PHP Testing Framework v2.5.6
Powered by PHPUnit 7.5.20 by Sebastian Bergmann and contributors.
Running with seed: 

Acceptance Tests (1) ---------------------------------------
AcceptanceCeCest: Test with split build command
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\AcceptanceCeCest:testWithSplitBuildCommand
Test: src/Test/Functional/Acceptance/AcceptanceCeCest.php:testWithSplitBuildCommand
Scenario --
 I cleanup work dir 
 I is cache work dir exists "master"
 I clone template to work dir "master"
 I create auth json 
 I create artifacts dir 
 I create artifact current tested code "ece-t...","2002...."
 I add artifacts repo to composer 
 I add dependency to composer "magento/ece-t...","2002.1.99"
 I add ece docker git repo to composer 
 I add cloud components git repo to composer 
 I add cloud patches git repo to composer 
 I add quality patches git repo to composer 
 I get dependency version "magento/magento-cloud-docker"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-components"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-patches"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/quality-patches"
 I add dependency to composer "magento/q...","dev-maste..."
 I assert true true,"Can not add dependency magento/qual..."
 I remove dependency from composer "magento/magento-clou..."
 I add dependency to composer "magento/product...","@stable"
 I composer update 
 I generate docker compose "--mode=production"
 I start environment 
 I run docker compose command "run build cloud-build"
 I run docker compose command "run deploy cloud-deploy"
 I am on page "/"

This comment was generated by Jenkins job ece-tools/functional build 55.

BarnyShergold commented 3 years ago

@leonhelmus - Left you some changes over a week ago - could we get an update please? You also need to sign the CLA

leonhelmus commented 3 years ago

@BarnyShergold Im not that familiar yet with the MTFT of magento and tomorrow is my vacation. I will try to get it done by today hope i will make it.

magento-cloud-ft-jenkins-svc commented 3 years ago

Unit & Integration Test Results

:white_check_mark:  All unit and integration tests have passed.

Unit Test Output

> phpunit --configuration tests/unit '--log-junit' 'tests/unit/tmp/junit.xml' '--coverage-clover' 'tests/unit/tmp/clover.xml'
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.

.............................................................   61 / 1513 (  4%)
.............................................................  122 / 1513 (  8%)
.............................................................  183 / 1513 ( 12%)
.............................................................  244 / 1513 ( 16%)
.............................................................  305 / 1513 ( 20%)
.............................................................  366 / 1513 ( 24%)
.............................................................  427 / 1513 ( 28%)
.............................................................  488 / 1513 ( 32%)
.............................................................  549 / 1513 ( 36%)
.............................................................  610 / 1513 ( 40%)
.............................................................  671 / 1513 ( 44%)
.............................................................  732 / 1513 ( 48%)
.............................................................  793 / 1513 ( 52%)
.............................................................  854 / 1513 ( 56%)
.............................................................  915 / 1513 ( 60%)
.............................................................  976 / 1513 ( 64%)
............................................................. 1037 / 1513 ( 68%)
............................................................. 1098 / 1513 ( 72%)
............................................................. 1159 / 1513 ( 76%)
............................................................. 1220 / 1513 ( 80%)
............................................................. 1281 / 1513 ( 84%)
............................................................. 1342 / 1513 ( 88%)
............................................................. 1403 / 1513 ( 92%)
............................................................. 1464 / 1513 ( 96%)
.................................................             1513 / 1513 (100%)

Time: 18.1 seconds, Memory: 82.50 MB

OK (1513 tests, 4762 assertions)

Generating code coverage report in Clover XML format ... done

Integration Test Output

> phpunit --configuration tests/integration '--log-junit' 'tests/integration/tmp/junit.xml'
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.

................................................................. 65 / 65 (100%)

Time: 3.96 seconds, Memory: 28.00 MB

OK (65 tests, 69 assertions)

This comment was generated by Jenkins job ece-tools/unit build 35.

magento-cloud-ft-jenkins-svc commented 3 years ago

Static Analysis & Code Style Results

:white_check_mark:  All static analysis and code style checks have passed.

PHP Codesniffer Output

> phpcs src --standard=tests/static/phpcs-ruleset.xml -p -n
............................................................  60 / 702 (9%)
............................................................ 120 / 702 (17%)
............................................................ 180 / 702 (26%)
............................................................ 240 / 702 (34%)
............................................................ 300 / 702 (43%)
............................................................ 360 / 702 (51%)
............................................................ 420 / 702 (60%)
............................................................ 480 / 702 (68%)
............................................................ 540 / 702 (77%)
............................................................ 600 / 702 (85%)
............................................................ 660 / 702 (94%)
..........................................                   702 / 702 (100%)

Time: 27.19 secs; Memory: 24MB

PHP Mess Detector Output


Found 0 violations and 0 errors in 19772ms

No mess detected

PHPStan Output

> phpstan analyse -c tests/static/phpstan.neon '--no-progress'

 [OK] No errors                                                                 

This comment was generated by Jenkins job ece-tools/static build 34.

leonhelmus commented 3 years ago

@BarnyShergold I have resolved all unit tests issues. I hope this is correct otherwise i will update my pull request in 2 weeks since i'm on vacation.

magento-cloud-ft-jenkins-svc commented 3 years ago

Functional Acceptance Test Results

:x:  One or more functional acceptance tests have failed.

PHP 7.1

PHP 7.2

PHP 7.3

PHP 7.4

Output for failed tests is below. If many tests have failed only the first 5 will be included. If you need additional information please reach out to the Magento Cloud team for more details.

This comment was generated by Jenkins job ece-tools/functional build 56.

magento-cloud-ft-jenkins-svc commented 3 years ago

PHP 7.4 AcceptanceCeCest Output

Codeception PHP Testing Framework v2.5.6
Powered by PHPUnit 7.5.20 by Sebastian Bergmann and contributors.
Running with seed: 

Acceptance Tests (1) ---------------------------------------
AcceptanceCeCest: Test with split build command
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\AcceptanceCeCest:testWithSplitBuildCommand
Test: src/Test/Functional/Acceptance/AcceptanceCeCest.php:testWithSplitBuildCommand
Scenario --
 I cleanup work dir 
 I is cache work dir exists "master"
 I clone template to work dir "master"
 I create auth json 
 I create artifacts dir 
 I create artifact current tested code "ece-t...","2002...."
 I add artifacts repo to composer 
 I add dependency to composer "magento/ece-t...","2002.1.99"
 I add ece docker git repo to composer 
 I add cloud components git repo to composer 
 I add cloud patches git repo to composer 
 I add quality patches git repo to composer 
 I get dependency version "magento/magento-cloud-docker"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-components"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-patches"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/quality-patches"
 I add dependency to composer "magento/q...","dev-maste..."
 I assert true true,"Can not add dependency magento/qual..."
 I remove dependency from composer "magento/magento-clou..."
 I add dependency to composer "magento/product...","@stable"
 I composer update 
 I generate docker compose "--mode=production"
 I start environment 
 I run docker compose command "run build cloud-build"
 I run docker compose command "run deploy cloud-deploy"
 I am on page "/"

This comment was generated by Jenkins job ece-tools/functional build 56.

BarnyShergold commented 3 years ago

@magento run FunctionalTests

BarnyShergold commented 3 years ago

@magento run Functional Tests

leonhelmus commented 3 years ago

@BarnyShergold so, no additional work is needed from me? We just have to wait for Magento?

BarnyShergold commented 3 years ago

@NadiyaS - One of the functional tests on this PR keeps failing but we can't see why. Can we get a pair of fresh eyes please?

BarnyShergold commented 3 years ago

@magento run Functional Tests

NadiyaS commented 3 years ago

@magento import pr to https://github.com/magento-commerce/ece-tools

m2-github-services commented 3 years ago

@NadiyaS the Pull Request is successfully imported.

NadiyaS commented 3 years ago

@BarnyShergold I imported PR and will check tests there.

NadiyaS commented 3 years ago

All tests passed in internal PR. Please update it with develop.

bbatsche commented 3 years ago

@BarnyShergold Could you please update this branch with develop and address my requested changes?

bbatsche commented 3 years ago

@leonhelmus Could you please address my review feedback and update this branch with develop?

leonhelmus commented 3 years ago

@bbatsche i will change it this week

magento-cloud-ft-jenkins-svc commented 3 years ago

Unit & Integration Test Results

:white_check_mark:  All unit and integration tests have passed.

Unit Test Output

> phpunit --configuration tests/unit '--log-junit' 'tests/unit/tmp/junit.xml' '--coverage-clover' 'tests/unit/tmp/clover.xml'
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.

.............................................................   61 / 1495 (  4%)
.............................................................  122 / 1495 (  8%)
.............................................................  183 / 1495 ( 12%)
.............................................................  244 / 1495 ( 16%)
.............................................................  305 / 1495 ( 20%)
.............................................................  366 / 1495 ( 24%)
.............................................................  427 / 1495 ( 28%)
.............................................................  488 / 1495 ( 32%)
.............................................................  549 / 1495 ( 36%)
.............................................................  610 / 1495 ( 40%)
.............................................................  671 / 1495 ( 44%)
.............................................................  732 / 1495 ( 48%)
.............................................................  793 / 1495 ( 53%)
.............................................................  854 / 1495 ( 57%)
.............................................................  915 / 1495 ( 61%)
.............................................................  976 / 1495 ( 65%)
............................................................. 1037 / 1495 ( 69%)
............................................................. 1098 / 1495 ( 73%)
............................................................. 1159 / 1495 ( 77%)
............................................................. 1220 / 1495 ( 81%)
............................................................. 1281 / 1495 ( 85%)
............................................................. 1342 / 1495 ( 89%)
............................................................. 1403 / 1495 ( 93%)
............................................................. 1464 / 1495 ( 97%)
...............................                               1495 / 1495 (100%)

Time: 17.96 seconds, Memory: 82.50 MB

OK (1495 tests, 4744 assertions)

Generating code coverage report in Clover XML format ... done

Integration Test Output

> phpunit --configuration tests/integration '--log-junit' 'tests/integration/tmp/junit.xml'
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.

................................................................. 65 / 65 (100%)

Time: 3.95 seconds, Memory: 28.00 MB

OK (65 tests, 69 assertions)

This comment was generated by Jenkins job ece-tools/unit build 50.

magento-cloud-ft-jenkins-svc commented 3 years ago

Static Analysis & Code Style Results

:white_check_mark:  All static analysis and code style checks have passed.

PHP Codesniffer Output

> phpcs src --standard=tests/static/phpcs-ruleset.xml -p -n
............................................................  60 / 697 (9%)
............................................................ 120 / 697 (17%)
............................................................ 180 / 697 (26%)
............................................................ 240 / 697 (34%)
............................................................ 300 / 697 (43%)
............................................................ 360 / 697 (52%)
............................................................ 420 / 697 (60%)
............................................................ 480 / 697 (69%)
............................................................ 540 / 697 (77%)
............................................................ 600 / 697 (86%)
............................................................ 660 / 697 (95%)
.....................................                        697 / 697 (100%)

Time: 26.01 secs; Memory: 24MB

PHP Mess Detector Output


Found 0 violations and 0 errors in 17572ms

No mess detected

PHPStan Output

> phpstan analyse -c tests/static/phpstan.neon '--no-progress'

 [OK] No errors                                                                 

This comment was generated by Jenkins job ece-tools/static build 49.

magento-cloud-ft-jenkins-svc commented 3 years ago

Functional Acceptance Test Results

:x:  One or more functional acceptance tests have failed.

PHP 7.1

:question:  No scenario results found

PHP 7.2

:question:  No scenario results found

PHP 7.3

:question:  No scenario results found

PHP 7.4

:question:  No scenario results found

Output for failed tests is below. If many tests have failed only the first 5 will be included. If you need additional information please reach out to the Magento Cloud team for more details.

This comment was generated by Jenkins job ece-tools/functional build 91.

leonhelmus commented 3 years ago

@bbatsche i dont know what i should do with those functional tests. I think i complied with everything now Could you please merge it?

bbatsche commented 3 years ago

The functional test errors are an issue internal to our Jenkins service and not a problem with your PR. I will have a fix or work around for it momentarily.

magento-cloud-ft-jenkins-svc commented 3 years ago

Functional Acceptance Test Results

:x:  One or more functional acceptance tests have failed.

PHP 7.2

PHP 7.3

PHP 7.4

Output for failed tests is below. If many tests have failed only the first 5 will be included. If you need additional information please reach out to the Magento Cloud team for more details.

This comment was generated by Jenkins job ece-tools/functional build 92.

magento-cloud-ft-jenkins-svc commented 3 years ago

PHP 7.4 AcceptanceCeCest Output

Codeception PHP Testing Framework v2.5.6
Powered by PHPUnit 7.5.20 by Sebastian Bergmann and contributors.
Running with seed: 

Acceptance Tests (1) ---------------------------------------
AcceptanceCeCest: Test with split build command
Signature: Magento\MagentoCloud\Test\Functional\Acceptance\AcceptanceCeCest:testWithSplitBuildCommand
Test: src/Test/Functional/Acceptance/AcceptanceCeCest.php:testWithSplitBuildCommand
Scenario --
 I cleanup work dir 
 I is cache work dir exists "master"
 I clone template to work dir "master"
 I create auth json 
 I create artifacts dir 
 I create artifact current tested code "ece-t...","2002...."
 I add artifacts repo to composer 
 I add dependency to composer "magento/ece-t...","2002.1.99"
 I add ece docker git repo to composer 
 I add cloud components git repo to composer 
 I add cloud patches git repo to composer 
 I add quality patches git repo to composer 
 I get dependency version "magento/magento-cloud-docker"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-components"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/magento-cloud-patches"
 I add dependency to composer "magento/m...","dev-devel..."
 I assert true true,"Can not add dependency magento/mage..."
 I get dependency version "magento/quality-patches"
 I add dependency to composer "magento/q...","dev-maste..."
 I assert true true,"Can not add dependency magento/qual..."
 I remove dependency from composer "magento/magento-clou..."
 I add dependency to composer "magento/product...","@stable"
 I composer update 
 I generate docker compose "--mode=production"
 I start environment 
 I run docker compose command "run build cloud-build"
 I run docker compose command "run deploy cloud-deploy"
 I am on page "/"

This comment was generated by Jenkins job ece-tools/functional build 92.

bbatsche commented 3 years ago

@magento import pr to https://github.com/magento-commerce/ece-tools

m2-github-services commented 3 years ago

@bbatsche an error occurred during the Pull Request import.

BaDos commented 3 years ago

@magento import pr to https://github.com/magento-commerce/ece-tools

m2-github-services commented 3 years ago

@BaDos an error occurred during the Pull Request import.

BaDos commented 3 years ago

@magento import pr to https://github.com/magento-commerce/ece-tools

m2-github-services commented 3 years ago

@BaDos the Pull Request is successfully imported.

leonhelmus commented 3 years ago

@BaDos amazing! You have beaten it 😁!

ghost commented 3 years ago

Hi @leonhelmus, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.