Hi @ilnytskyi. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.

❗ 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.

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

@magento run all tests

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.

OMG wow why would unit test check config with not existing parameters for requested type and allow test to pass?
\Magento\Framework\ObjectManager\Test\Unit\Factory\Fixture\Compiled\SimpleClassTesting::__construct

Shouldn't OM work this way that it reads config from di.xml and/or resolves based on reflection then just passes the unpack arguments to new $instance(...$args).
I you defined extra arguments in di.xml looks like they are ignored now, but this test failure would confirm that di compilation must fail for this case due to invalid di.xml. This way di.xml becomes stricter.

There were 2 errors:

1) Magento\Framework\ObjectManager\Test\Unit\Factory\CompiledTest::testCreateSimple
Error: Unknown named parameter $value_array

2) Magento\Framework\ObjectManager\Test\Unit\Factory\CompiledTest::testCreateSimpleConfiguredArguments
Error: Unknown named parameter $value_array

@ilnytskyi I think it was working like that in the pre-php8 era, so it kept like that due to compatibility reasons (earlier it was working by argument position, not by argument name, and you might have the wrong argument name).
So I think that was a hack, that we should remove to get performance benefit.
Please investigate deeper test failures

@magento run all tests

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 run all tests

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 run Functional Tests EE, Integration Tests, WebAPI Tests

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

@magento run all tests

Hi @ilnytskyi

Thanks for the contribution!

✔️ QA Passed
Preconditions:

Install fresh Magento 2.4-develop

Steps to reproduce

• Follow the description.
• Run the following commands:
  bin/magento setup
  bin/magento s:d:c
  bin/magento c:f
  (All commands should run successfully.)

Before: ✖️
N/A

After✔️:

Execution of Array Values and Named Values.

Builds are failed. Hence, moving this PR to Extended Testing.

Thanks

@magento run Unit Tests, Functional Tests EE, Functional Tests B2B

@magento run all tests

@magento run Functional Tests B2B

Functional test B2B failures are different in the last two runs.

Run 1:
https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/37411/e9afb79fa478da24ca41fbaa67d7ff8a/Functional/allure-report-b2b/index.html#categories/39002bb4b823f2d59e22404a186a7115/893c875ee0add438/

Run 2:
https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/37411/796611e6a5f111b2d24956a7a4aa81f7/Functional/allure-report-b2b/index.html#categories/8204e1939c11cfc5dade2a6cfc331ffe/ca132cb54a1bbf19/

So moving it to merge in progress.

@magento create issue