Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 52031 - Building workspace is getting flagged as a system job
Summary: Building workspace is getting flagged as a system job
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M8   Edit
Assignee: John Arthorne CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-13 19:23 EST by Stefan Xenos CLA
Modified: 2004-03-03 17:25 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Xenos CLA 2004-02-13 19:23:43 EST 
M7

The background build job is getting flagged as a system job. This is preventing
it from appearing in the progress view by default.
Comment 1 John Arthorne CLA 2004-02-16 11:56:53 EST 
The autobuild job should only be a system job when autobuild is turned off (the
job still needs to run in this case to fire build events).  Was autobuild on or
off in your case?
Comment 2 Stefan Xenos CLA 2004-02-17 13:29:16 EST 
No. Autobuild was turned on...

However, I occasionally use ctrl-B to force a build. If it opens a dialog
telling me that a build is currently running, I cancel it. I'm not sure if this
occurred this particular time, but I'm noticing that this problem is happening
quite frequently in my workspace.
Comment 3 John Arthorne CLA 2004-03-03 11:24:08 EST 
I have seen this happen in I20040302.  Will investigate...
Comment 4 Tod Creasey CLA 2004-03-03 11:40:57 EST 
I get the same problem straight from download.
Comment 5 Tod Creasey CLA 2004-03-03 11:41:28 EST 
It is post M7 for me though. Didn't happen until 20040303 (or at least I 
didn't notice until then).
Comment 6 John Arthorne CLA 2004-03-03 17:25:37 EST 
The bug has been around forever, but the workbench's cycling of autobuild off
and on during startup was "fixing" it (I listen for autobuild state change and
set the autobuild as a system job only when autobuild is off). Fixed. This won't
be released for integration rebuilds this week because there are a large number
of untested changes in HEAD that we don't want to release yet.  Will appear next
week.  As a workaround, cycle autobuild off and on manually to get things into a
normal state.