-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration tests fail massively #914
Comments
Ups, I got it. Refreshing the test database to match the current m2 version helps. |
Ups, too early. That didn't help after all :( |
Try to cleanup everything before running tests:
Maybe DB cleanup doesn't work properly or/and you have old generated files and they are not removed automatically. |
Thanks, one of those 3 almost did the trick. Now 29% of the integration tests execute without errors, even though many fail.
Again I'm wondering how this is different from how travis is executing the integration tests. |
Hm. I wonder, why PHPUnit says that it reads information from |
Yes, interesting. I have added a phpunit.xml with the only difference to the phpunit.xml.dist being 1G available memory for running the tests. % diff -u phpunit.xml.dist phpunit.xml ✭
--- phpunit.xml.dist 2015-01-05 15:44:51.000000000 +0100
+++ phpunit.xml 2015-01-05 23:39:34.000000000 +0100
@@ -38,6 +38,7 @@
<includePath>testsuite</includePath>
<ini name="date.timezone" value="America/Los_Angeles"/>
<ini name="xdebug.max_nesting_level" value="200"/>
+ <ini name="memory_limit" value="1024M"/>
<!-- Local XML configuration file ('.dist' extension will be added, if the specified file doesn't exist) -->
<const name="TESTS_INSTALL_CONFIG_FILE" value="etc/install-config-mysql.php"/>
<!-- Semicolon-separated 'glob' patterns, that match global XML configuration files --> |
Hey @Vinai, any luck with tests? They are straight forward, did you specify DB connection, last errors looks like no DB connected. |
Thanks for checking in. Yes, I have the DB connection configured. WIthout it the integration tests abort before the first test is executed. |
If you clean all required folders, drop DB and create new empty one. Then launching tests - what last error do you have. |
Here is what I get
And thats it. |
Did you try to skip the test and run without it? Wonder if it is specific test issue. Trying to reproduce. |
@Vinai, i have fresh cloned magneto2, cleaned up everything in var/*, and and tests passed well. |
I've tried the following:
Here is my install-config-mysql.php file: <?php
return [
'db_host' => 'localhost',
'db_user' => 'm2-test-db-user',
'db_pass' => 'not-my-password',
'db_name' => 'magento_integration_tests',
'db_prefix' => '',
'backend_frontname' => 'backend',
'admin_username' => \Magento\TestFramework\Bootstrap::ADMIN_NAME,
'admin_password' => \Magento\TestFramework\Bootstrap::ADMIN_PASSWORD,
'admin_email' => \Magento\TestFramework\Bootstrap::ADMIN_EMAIL,
'admin_firstname' => \Magento\TestFramework\Bootstrap::ADMIN_FIRSTNAME,
'admin_lastname' => \Magento\TestFramework\Bootstrap::ADMIN_LASTNAME,
]; I'll try skipping the test that kills the process tomorrow. But still, so many other tests are already marked as failed that seem to run smoothly in travis. |
@Vinai , could you, please, try to disable these extensions? And if it doesn't help, could you run the tests with |
Progress, even though I can't explain some of it.
Result: a few errors and failed tests, but much fewer. Next I enabled only the xdebug zend extension and repeated steps 2-4 For the next step I enabled also the opcache zend extension and repeated steps 2-4 again. Finally I also enabled the uopz extension again and ran the tests again. So now I have effectively the same set up as last night, but a different outcome. The remaining number of errors and failures was small enough that I decided to have a detailed look why they where failing. The remaining tests I was able to fix by using a custom phpunit.xml with 1GB of memory. Going back to my "main" m2 dev instance, the integration tests now also run. I found additional failures due to invalid themes I had created, which I was able to fix without much trouble. I'm puzzled and not sattisfied by not knowing what was causing the issue, but it obviously must have been due to my local setup. However, now that it is resolved I can focus on more important things. |
MSI-891: Stock status title is visible on "Advanced Inventory" in multi source mode
Currently I'm unable to run the integration tests.
Steps to reproduce:
I have to assign 1G memory to PHP to make them run, but even then pretty much every test gives me a stacktrace.
The same happens if I call phpunit directly without the tests.php script.
And its not always the same stacktrace. Some are due to Magento\RecurringPayment missing, but some others seem completely unrelated to the payment methods.
See below at the bottom of this issue for a few examples.
What I don't get is why the integration tests on travis run.
Any idea what I am doing wrong? Was something changed recently in how to run the integration tests?
Here a couple examples of from the exceptions and errors:
The text was updated successfully, but these errors were encountered: