Community
Participate
Working Groups
org.eclipse.egit.core.test.op.CloneOperationTest.testConfigureFetchAfterCloneTask fails on Windows (because of some pack file still being locked). It succeeds if the ListNotesCommand in line 193 is not called. Be aware that in the same test an AddNoteCommand is called (line 201) without causing an issue. Since someone fixed all the other issues related to pack files, maybe this is worth an investigation, too? If the issue cannot be fixed easily, would others be okay with using JUnit Assume to not execute this test on Windows? I would really like to see a fully green test execution on Windows (even with using Assume) before starting to switch to JUnit 5.
The tests in CloneOperationTest all neglect to close the cloned repo. They should.
(In reply to Thomas Wolf from comment #1) > The tests in CloneOperationTest all neglect to close the cloned repo. They > should. I think that's okay. The repository1 member is a protected one and will be cleaned up by the super class. Also it is really sufficient to remove the line 193 to make _all_ test cases become green (while 4 are red for me right now).
I'm not talking about repository1. I'm talking about the clone created from that.
New Gerrit change created: https://git.eclipse.org/r/161088
Gerrit change https://git.eclipse.org/r/161088 was merged to [master]. Commit: http://git.eclipse.org/c/egit/egit.git/commit/?id=e1a202faf9b2811c75bbe7f100930d28302120ae