Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 475623 - Dry run in push configuration leads to unsable Eclipse
Summary: Dry run in push configuration leads to unsable Eclipse
Status: CLOSED DUPLICATE of bug 391182
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-22 00:37 EDT by Lars Vogel CLA
Modified: 2015-09-14 14:47 EDT (History)
3 users (show)

See Also:


Attachments
Screenshot (193.56 KB, image/png)
2015-08-22 00:37 EDT, Lars Vogel CLA
no flags Details
Screenshot (221.78 KB, image/png)
2015-09-08 05:52 EDT, Lars Vogel CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Vogel CLA 2015-08-22 00:37:32 EDT
Created attachment 256029 [details]
Screenshot

If I press "Dry run" in the push configuration I get two popups and I cannot close either on of them. Pressing "Cancel" on the first one, makes Eclipse unresponsive.
Comment 1 Lars Vogel CLA 2015-09-08 05:51:29 EDT
Matthias, Andrey, this happens all the time if I change the push configuration and press "Dry-Run".
Comment 2 Lars Vogel CLA 2015-09-08 05:52:20 EDT
Created attachment 256433 [details]
Screenshot
Comment 3 Andrey Loskutov CLA 2015-09-08 07:02:52 EDT
Lars, can you please create stack trace from "hanging" eclipse? Are you using 4.6 dev. build or "official" 4.5?
Comment 4 Lars Vogel CLA 2015-09-08 07:12:04 EDT
(In reply to Andrey Loskutov from comment #3)
> Lars, can you please create stack trace from "hanging" eclipse? Are you
> using 4.6 dev. build or "official" 4.5?

I have seen that in customer training sessions with 4.5 and 4.6. Did you try? Should be easy to reproduce.
Comment 5 Andrey Loskutov CLA 2015-09-14 14:47:47 EDT
Seems to be a dup of bug 391182 comment 1.

*** This bug has been marked as a duplicate of bug 391182 ***