Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335452 - [launching] Progress Bar stuck at 57% when executing long running external tool
Summary: [launching] Progress Bar stuck at 57% when executing long running external tool
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 4.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-26 10:18 EST by Marko Tomljenovic CLA
Modified: 2019-11-14 02:18 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marko Tomljenovic CLA 2011-01-26 10:18:16 EST
Build Identifier: 3.6.1

We are using the "Run external tools" mechanism to execute some long running batch jobs.

What happens is that the progress bar always is stuck at 57% for a long time until the execution is finally finished. This irritates our users since they think that the execution is really stuck.

What I would expect is that the progress bar moves from right to left and vice versa like it is usually done when the progress monitor ticks are not specified in a job/runnablewithprogress.

Reproducible: Always

Steps to Reproduce:
1. Create a "External Tool" launch configuration
2. The configuration shall execute a batch that runs for a lon time (e.g. few minutes)
3. Execute the launch configuration
Comment 1 Michael Rennie CLA 2011-01-26 11:20:52 EST
Platform Ant owns the launching code for external tools
Comment 2 Lars Vogel CLA 2019-11-14 02:18:32 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.