Bug #37435
Functional Domain/NodesTest fail with 2 Errors
Status: | Resolved | Start date: | 2012-05-23 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | Christian Müller | % Done: | 100% |
|
Category: | Node handling | |||
Target version: | - |
Description
Functional Testing fails with the following messages:
There were 2 failures: 1) TYPO3\TYPO3CR\Tests\Functional\Domain\NodesTest::renumberingTakesUnpersistedNodeOrderChangesIntoAccount Expected node node003 (index 3), actual node node004 (index 5) /var/www/Packages/Application/TYPO3.TYPO3CR/Tests/Functional/Domain/NodesTest.php:552 /var/www/Packages/Application/TYPO3.TYPO3CR/Tests/Functional/Domain/NodesTest.php:500 /var/www/Packages/Framework/TYPO3.FLOW3/Tests/BaseTestCase.php:50 2) TYPO3\TYPO3CR\Tests\Functional\Domain\NodesTest::nodeRepositoryRenumbersNodesIfNoFreeSortingIndexesAreAvailable Expected node node150 (index 800), actual node node149 (index 7900) /var/www/Packages/Application/TYPO3.TYPO3CR/Tests/Functional/Domain/NodesTest.php:552 /var/www/Packages/Application/TYPO3.TYPO3CR/Tests/Functional/Domain/NodesTest.php:526 /var/www/Packages/Framework/TYPO3.FLOW3/Tests/BaseTestCase.php:50 FAILURES! Tests: 20, Assertions: 30, Failures: 2.
Maybe you have that, too; System is Debian Sqeeze with PHP 5.4 (!)
History
#1 Updated by Christian Müller about 3 years ago
- Status changed from New to Accepted
- Assigned To set to Christian Müller
Already identified the problem and have a possible fix ready. Needs a bit of cleanup before pushing
#2 Updated by Karsten Dambekalns about 3 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100