Bug 96575 - Fail to build on workspace restart after upgrade
Summary: Fail to build on workspace restart after upgrade
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2 M6   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-25 05:33 EDT by Jerome Lanneluc CLA
Modified: 2006-03-27 06:55 EST (History)
1 user (show)

See Also:


Attachments
Builder trace since the begining of the session (11.79 KB, text/plain)
2005-05-25 05:34 EDT, Jerome Lanneluc CLA
no flags Details
Builder trace for N20050526 (464.24 KB, text/plain)
2005-05-26 04:40 EDT, Jerome Lanneluc CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jerome Lanneluc CLA 2005-05-25 05:33:37 EDT
N20050525

1. I was running my development workspace with N20050424.
2. I have autobuild off
3. I exited my workspace. The exit happened normaly (no workspace crash).
4. I restarted the same workspace with N20050525
5. I replaced org.eclipse.jdt.ui.tests and org.eclipse.jdt.ui.tests.refactoring
with date 'May 25, 2005 00:10 EST'.
6. I pressed the build button
7. It started doing full builds (as expected) but it failed to rebuild the
dependent projects of org.eclipse.jdt.core, each having the following message:
'The project cannot be built until its prerequesite org.eclipse.jdt.core is built.'
Comment 1 Jerome Lanneluc CLA 2005-05-25 05:34:30 EDT
Created attachment 21703 [details]
Builder trace since the begining of the session
Comment 2 Kent Johnson CLA 2005-05-25 12:01:28 EDT
No luck reproducing the trace... I suspect the missing build state files may 
explain why jdt.core was not built at all.

Access rule changes to core.runtime are causing full builds in the 'upgrade 
tests' I tried, but each project was able to find its build state & rebuilt 
successfully.


These are the options I'm running with:

# Turn on debug tracing for org.eclipse.jdt.core plugin
org.eclipse.jdt.core/debug=true
# Reports incremental builder activity : nature of build, built state reading, 
indictment process
org.eclipse.jdt.core/debug/builder=true

# Turn on debugging for the org.eclipse.core.resources plugin.
org.eclipse.core.resources/debug=true
# Reports the start and end of all builder invocations
org.eclipse.core.resources/build/invoking=true
Comment 3 Jerome Lanneluc CLA 2005-05-26 04:40:34 EDT
Created attachment 21799 [details]
Builder trace for N20050526

After I upgraded from N20050525 to N20050526, I got a full build (as expected)
but  this time jdt.core was correctly built (and dependent projects as well).

However not that the previous build state was still not found, and the trace
still doesn't show were the build state is supposed to be.
Comment 4 Jerome Lanneluc CLA 2005-05-26 04:42:40 EDT
Also this looks very suspicious:

Starting build of org.eclipse.jdt.core @ Thu May 26 10:30:10 CEST 2005
About to read state...
Successfully read state for org.eclipse.text <--- !!!!!!!!!
Performing full build since last saved state was not found
FULL build
Comment 5 Jerome Lanneluc CLA 2005-05-26 09:02:06 EDT
It might be a race condition between the external jar refresh that is done in a
separate job on start up, and the builder.

Changed DeltaProcessor#checkExternalArchiveChanges(...) to touch all the
affected projects at once (by taking the workspace lock). Also the build state
is reset at the same time, but this should be removed when we have support for
external jars timestamps in the build state.
Comment 6 Kent Johnson CLA 2005-06-06 13:52:34 EDT
Please reopen if the problem persists with the latest builds
Comment 7 Philipe Mulet CLA 2006-03-27 06:54:51 EST
reopening to close, since never reproduced in a long time
Comment 8 Philipe Mulet CLA 2006-03-27 06:55:05 EST
closing