-
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
Unit tests are failing with libxml 2.9.10 #34733
Comments
Hi @ihor-sviziev. Thank you for your report.
Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
For more details, review the Magento Contributor Assistant documentation. Add a comment to assign the issue: To learn more about issue processing workflow, refer to the Code Contributions.
🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket. 🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
Hello @ihor-sviziev |
Thats reporting issue (from Jenkins to GitHub). Tests are running in different groups in few threads. Total number of reported OpenSource php unit tests is 26011 |
From what I see most of the failures in your results related to xml\xsd. Please double check that everything is ok on that environment |
@xmav, please ping me in Slack, it will be way faster to check it |
After discussion with @xmav in Slack - it feels like the current tests work with outdated libxml2 library version 2.9.1, while on Ubuntu 20.04 we have 2.9.10 or 2.9.12. After downgrading to libxml 2.9.4 (used Debian buster based installation) everything works fine. Just a side note: on local env unit tests are running for 2 minutes. Why the hell they're running for 30+ mins on the CI? |
I confirm this issue on Debian bullseye / libxml 2.9.10 on M2.4.4. (2.9.4 is not available on standard bullseye) |
For others running in docker and facing this issue, until this is fixed in the core, sharing my small hack; Running in a FROM php:8.1-fpm-alpine
## LIBXML 2.9.4 for Magento unit tests (https://github.com/magento/magento2/issues/34733)
RUN apk add --no-cache --virtual .build-deps build-base automake libtool zlib-dev autoconf make && \
apk del libxml2-dev && \
curl https://gitlab.gnome.org/GNOME/libxml2/-/archive/v2.9.4/libxml2-v2.9.4.zip -o /tmp/libxml.zip && \
cd /tmp && \
unzip libxml.zip && \
cd libxml2-v2.9.4 && \
./autogen.sh && \
make && \
make install && \
apk del --no-network .build-deps && \
rm /usr/lib/libxml2.so.2 && \
ln -s /usr/local/lib/libxml2.so.2.9.4 /usr/lib/libxml2.so.2 Make sure you test this before you use this in production, use at your own risk. |
Hi @engcom-Lima. Thank you for working on this issue.
|
Hi @engcom-Dash. Thank you for working on this issue.
|
Hi @ihor-sviziev , We are trying to reproduce the issue in 2.4-develop instance.But we are not able to reproduce the issue. Magento Version -2.4 develop Steps to Reproduce: As per the description there are 153 failures was occurred. But we got 23 Failures only occurred.We are not able to reproduce the issue. Let us know if we missing anything!!! Thanks!!!! |
✅ Jira issue https://jira.corp.adobe.com/browse/AC-8018 is successfully created for this GitHub issue. |
✅ Confirmed by @engcom-November. Thank you for verifying the issue. |
❌ You don't have permission to export this issue. |
Hi @ihor-sviziev, We got Confirmation from internal team. We have run 2 jenkins build on baseimages/centos7php82os2mysql80 & baseimages/centos7php81os2mysql80 There are no failures observed. Hence this issue which is created is no longer reproducible. Screenshots for reference: Thanks. |
hi @engcom-Bravo,
And locally, in warden, I have exactly the same issue. Note: I rebased my branch on top of current 2.4-develop branch and updated it to use PHP 8.1 2.4-develop...ihor-sviziev:run-unit-tests |
So since this issue isn't reproducing anymore, I'm closing it. But keep in mind. The tests still failing |
Preconditions (*)
Steps to reproduce (*)
composer install
vendor/bin/phpunit -c dev/tests/unit/phpunit.xml.dist
Expected result (*)
Actual result (*)
Failures (I have 153 failures, I give you only one for example) :
Additional Information
Same issue is reported here. Launching Unit tests with M2.4.4 and PHP8.1 gives errors and failures
Additional Notes
platform-health
branch):platform-health...ihor-sviziev:run-unit-tests
You can find the result of the execution here:
https://github.com/ihor-sviziev/magento2/runs/4353240450?check_suite_focus=true
Example: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/34723/e5b7c4fa8fbdcd87b9a7e2551dc072ab/Unit/console-error-logs.html
At the end of CE tests
But when we're running tests locally, we have the following output (4X more tests were run!):
/CC @andrewbess @xmav
Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.
The text was updated successfully, but these errors were encountered: