| Summary: | Failure in GitCloneTest: expected:<[Error cloning git repository]> but was:<[/tmp/80525576121: not found.]> | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Malgorzata Janczarska <malgorzata.tomczyk> |
| Component: | Git | Assignee: | Malgorzata Janczarska <malgorzata.tomczyk> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | john.arthorne |
| Version: | 0.5 | ||
| Target Milestone: | 0.5 RC2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Malgorzata Janczarska
This isn't intermittent. It fails consistently when running with the latest JGit. The test is relying on the specific text of the message coming from JGit. JGit has been changing their exception code which caused this to change. Also the "main" exception being surfaced back to the caller is either our own message, or the JGit message if there is one. I think we should always prefer our own message because it is higher level and more meaningful to the end user (in this case, "Error cloning repository" versus "File not found"). I have released a fix in the hope of getting a clean RC1 build: http://git.eclipse.org/c/orion/org.eclipse.orion.server.git/commit/?id=f3373dac3e48de6d6221c022d3a8930637841dd6 I will leave this bug open for Szymon or Gosia to sanity check my fix. The fix is OK for now, but I will change it in RC2 to return more useful details to the user. (In reply to comment #3) > The fix is OK for now, but I will change it in RC2 to return more useful details > to the user. I added handling the new GitApiException to return more accurate information to the user. "Invalid remote: origin" message is back in DetailedMessage. As much as I don't like asserting messages I have to admit that this is better than "/tmp/80525576121: not found." and the test helped us find it. |