Re: [platform-releng-dev] PROBLEM: [eclipse-build]Build I20111208-1305 (

[Kim Moir <Kim_Moir@xxxxxxxxxx>]

Dani,

I didn't run a test build yesterday
at v20111208-1136.  I don't run the tagging portion when we run test
builds.  

The jdt.doc ckhpii fix was released
after the build started at 13:05.  So that change shouldn't be there.
 

Please manually retag so we can start
another build and I'll look at the scripts in the interim to see what's
happening.

Also, I've stopped the 8am maintenance
build and will run it after we have an integration build 

Kim



From:      
 Daniel Megert <daniel_megert@xxxxxxxxxx>
To:      
 "Eclipse platform
release engineering list." <platform-releng-dev@xxxxxxxxxxx>,
Kim Moir/Ottawa/IBM@IBMCA
Date:      
 12/09/2011 03:36 AM
Subject:    
   [platform-releng-dev]
PROBLEM: [eclipse-build]Build I20111208-1305 (Timestamp: 201112081305):Build
is complete. Automated JUnit testing is starting.
Sent by:    
   platform-releng-dev-bounces@xxxxxxxxxxx

---

Huston, we have a problem: something
is wrong with our auto-tag script! 

Changes merged into http://git.eclipse.org/c/jdt/eclipse.jdt.ui.git/log/?h=integration
are not in this latest build. The strange thing is that there is a new
tag ('v20111208-1136' - oddly enough the time stamp for this tag is 2011-12-08,
13:26) on the tip of 'integration', but this tag is not (and was not) used
in the 'jdtui.map' file. Kim, can you explain this tag? Could it come from
a test build? If so, I don't understand the time stamp i.e. why it is not
closer to the tag name. Maybe the script is broken and aborts when it sees
a tag at the tip of 'integration' and does not verify that it is actually
used in the map file? Maybe the comparator that decides whether a change
was made is broken (the change was in a *.properties file)?

'org.eclipse.jdt.doc.user' has the same problem: 
    plugin@xxxxxxxxxxxxxxxxxxxxxxxx=GIT,tag=v20111205-0928,...
   plugin@xxxxxxxxxxxxxxxxxxxxxxx=GIT,tag=v20111208-1301,...
==> the script did not detect that there is a change in 'eclipse.jdt.doc.user'.
Now, this incident could be caused by the manual tagging that was done
on 'org.eclipse.jdt.doc.isv' to ensure that Javadoc gets re-built. If the
script aborts when it finds the tag on the tip of 'integration' in the
'doc.map' file (which could be an acceptable strategy), then this would
explain it. 

More contributions might be missing in the latest build. Everyone should
check whether the contributions from this week are indeed in the build.

If we can't quickly figure out what's wrong with the script, then I suggest
we manually tag the affected projects and rebuild.

Dani

From:	Kim_Moir@xxxxxxxxxx
To:	platform-releng-dev@xxxxxxxxxxx
Date:	08.12.2011 23:16
Subject:	[platform-releng-dev] [eclipse-build]Build I20111208-1305        (Timestamp: 201112081305):Build is complete. Automated JUnit        testing is starting.

---

Build I20111208-1305 (Timestamp: 201112081305):  The build is complete.

HTTP Download:

http://download.eclipse.org/eclipse/downloads/drops/I20111208-1305

The Build is complete.  Automated JUnit testing is starting.

HTTP Download:

http://download.eclipse.org/eclipse/downloads/drops/I20111208-1305


_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev


_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev