Skip to content

Update ramsey/uuid to php8 compatible version #32614

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

Merged

Conversation

ihor-sviziev
Copy link
Contributor

@ihor-sviziev ihor-sviziev commented Mar 29, 2021

Description (*)

Right now not all dependencies are ready.
Issues:

For now, I get it resolved using aliases.
I executed following commands:

composer require ramsey/uuid allure-framework/allure-codeception:"1.5.0 as 1.4.5" allure-framework/allure-phpunit:"dev-master as 1.3.2" --update-with-dependencies
composer require --dev allure-framework/allure-codeception:"1.5.0 as 1.4.5" allure-framework/allure-phpunit:"dev-master as 1.3.2"

Also, I replaced in all places Yandex\Allure\Adapter\AllureAdapter with Yandex\Allure\PhpUnit\AllurePhpUnit, as class was renamed between these versions: https://github.com/allure-framework/allure-phpunit/compare/1.2.4..1.3.1

Requires MFTF changes from magento/magento2-functional-testing-framework#825

Related Pull Requests

https://github.com/magento/partners-magento2ee/pull/538

Fixed Issues (if relevant)

  1. Fixes Update ramsey/uuid dependency to PHP 8 compatible version #31777

@m2-assistant
Copy link

m2-assistant bot commented Mar 29, 2021

Hi @ihor-sviziev. Thank you for your contribution
Here are some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me php8-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests
  13. Semantic Version Checker

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please 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

@ihor-sviziev
Copy link
Contributor Author

@magento run all tests

@m2-community-project m2-community-project bot added the Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. label Mar 29, 2021
@ihor-sviziev
Copy link
Contributor Author

@magento run Static Tests, Unit Tests

@ihor-sviziev
Copy link
Contributor Author

@magento run all tests

@ihor-sviziev
Copy link
Contributor Author

@magento run Functional Tests EE, Integration Tests

Install magento functional tests from PR
@ihor-sviziev
Copy link
Contributor Author

@magento run all tests

@ihor-sviziev
Copy link
Contributor Author

@magento run all tests

@sivaschenko
Copy link
Member

Update of allure-framework/allure-phpunit version #31296

Install magento functional tests from php8-develop branch
@ihor-sviziev
Copy link
Contributor Author

@magento run all tests

@ihor-sviziev ihor-sviziev changed the base branch from php8-develop to 2.4-develop April 12, 2021 12:39
@ihor-sviziev
Copy link
Contributor Author

ihor-sviziev commented Apr 13, 2021

Finally! we can update the allure/allure-phpunit package!
allure-framework/allure-phpunit#52 (comment)
https://packagist.org/packages/allure-framework/allure-phpunit#1.4.0

…msey/uuid

# Conflicts:
#	composer.json
#	composer.lock
Update allure-framework/allure-phpunit to stable version
@ihor-sviziev
Copy link
Contributor Author

@magento run all tests

@ihor-sviziev
Copy link
Contributor Author

ihor-sviziev commented Apr 13, 2021

Basically, this PR is waiting for:

@ihor-sviziev ihor-sviziev marked this pull request as ready for review April 21, 2021 09:29
@sivaschenko
Copy link
Member

#31296 is merged, I will update composer.json and lock and add the EE PR

@sivaschenko
Copy link
Member

@magento run Static Tests

@ihor-sviziev
Copy link
Contributor Author

@magento run all tests

@ihor-sviziev ihor-sviziev changed the title [WIP] Update ramsey/uuid to php8 compatible version Update ramsey/uuid to php8 compatible version Apr 28, 2021
@ihor-sviziev
Copy link
Contributor Author

@magento run Integration Tests

@ihor-sviziev
Copy link
Contributor Author

@magento run Functional Tests EE

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@Den4ik
Copy link
Contributor

Den4ik commented May 5, 2021

@ihor-sviziev could you please resolve conflict

@sivaschenko
Copy link
Member

@ihor-sviziev MFTF 3.5.1 is released. Updated the PR and rerunning the tests

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@ihor-sviziev
Copy link
Contributor Author

@magento run WebAPI Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@magento-engcom-team
Copy link
Contributor

Hi @sivaschenko, thank you for the review.
ENGCOM-9073 has been created to process this Pull Request
✳️ @sivaschenko, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

@magento-engcom-team magento-engcom-team merged commit 94cc576 into magento:2.4-develop May 8, 2021
@m2-assistant
Copy link

m2-assistant bot commented May 8, 2021

Hi @ihor-sviziev, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Composer Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: ready for testing Project: PHP8 Release Line: 2.4
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update ramsey/uuid dependency to PHP 8 compatible version
4 participants