Bug #65315
Epic #65314: PHP7
ExtractorRegistryTest::registeredExtractorClassWithSamePriorityAreReturnedInSameOrderAsTheyWereAdded
| Status: | Resolved | Start date: | 2015-02-25 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | 7 LTS | |||
| TYPO3 Version: | 6.2 | Is Regression: | No | |
| PHP Version: | 7.0 | Sprint Focus: | ||
| Complexity: |
Description
TYPO3\CMS\Core\Tests\Unit\Resource\Index\ExtractorRegistryTest::registeredExtractorClassWithSamePriorityAreReturnedInSameOrderAsTheyWereAdded
Failed asserting that false is true.
/home/opitz/projects/typo3-master/typo3-src/typo3/sysext/core/Tests/Unit/Resource/Index/ExtractorRegistryTest.php:117
/home/opitz/projects/neos-git/Packages/Libraries/phpunit/phpunit/phpunit:58
=> usort handling changed, 5.x same will be swapped => 7.0 same won't be swapped
=> Same on HHVM
This needs fix in our sorting function, it is in PHP documented that sorting result of same is not defined. Till yet we hope that sorting is same.
History
#1 Updated by Alexander Opitz 5 months ago
- Description updated (diff)
#2 Updated by Susanne Moog 18 days ago
- Status changed from New to Resolved
This is resolved in current master. The old behaviour stayed inside and we changed the tests to be "sorting agnostic" when testing same priority instances.
