TYPO3 Core

2015-01-21

Bug #64644: Failling unit test in GeneralUtilityTest for Windows system

Closed

2015-01-30

Bug #64651: Failling unit test in DatabaseConnectionTest

Closed

2015-01-30

Bug #64656: Failing unit tests due to wrong path handling

Closed

2015-01-30

Bug #64657: Failing unit test in SqlSchemaMigrationServiceTest on Windows systems

Closed

2015-01-30

Bug #64661: DateValidator fails to validate incorrect dates

Closed

2015-01-30

History
Notes
Property changes

Actions

See http://wiki.typo3.org/Contribution_Walkthrough_Tutorials

Updated by Michael Stucki over 11 years ago

We obviously lack more programmers with a Windows server.

May I invite you to try to fix some of the issues yourself, and provide the patches to us?

If you need further help, let me know.

Actions

Updated by Gerrit Code Review over 11 years ago

Status changed from New to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14896

Actions

Updated by Gerrit Code Review over 11 years ago

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14896

Actions

Updated by Nicole Cordes over 11 years ago

Still errors in:

TYPO3\CMS\Core\Tests\Functional\Category\Collection\CategoryCollectionTest
TYPO3\CMS\Core\Tests\Unit\Resource\Driver\LocalDriverTest
TYPO3\CMS\Core\Tests\Unit\Utility\File\ExtendedFileUtilityTest

TYPO3\CMS\Dbal\Tests\DatabaseGeneralTest
TYPO3\CMS\Dbal\Tests\DatabaseOracleTest

TYPO3\CMS\Frontend\Tests\Unit\ContentObject\ContentObjectRendererTest

Actions

Updated by Alexander Opitz almost 10 years ago

Status changed from Under Review to New
Target version deleted (~~6.0.0~~)
Is Regression set to No

Hi Nicole,

you abandoned the patch and mentioned that this is fixed in several other patches. So close this issue?

Actions

Updated by Wouter Wolters over 9 years ago

Status changed from New to Closed

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions