Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-releng-dev] PROBLEM: [eclipse-build]Build I20111208-1305 (Timestamp: 201112081305):Build is complete. Automated JUnit testing is starting.

On Fri, Dec 9, 2011 at 3:35 AM, Daniel Megert <daniel_megert@xxxxxxxxxx> wrote:
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',

When I look at eclipse.jdt.ui, I see:
commit 8cf0ece7695dbbe9bbebfcd3d1f44b601b205619 (HEAD, v20111208-1136, origin/master, origin/integration, origin/HEAD, master)
Author: Dani Megert <dmegert>
Date:   Thu Dec 8 12:36:30 2011 +0100

So my conversion into UTC will give the v20111208-1136 you see.

 
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?

it looks like the auto-tagging script has its final push (on eclipse.platform.releng.maps) disabled.  So it created the timestamps on the build input and probably has the correct maps update in the auto-tagging repo, but wasn't pushed.


'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.


the script will compare each plugin and feature in the map file to the last commit that touched that project in the repo.  If the map file tag "contains" the last commit for that project, it does nothing for that project ... but it will still process all the others.
 

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

Yes, the last 3 contributions to eclipse.platform.ui got tagged but not included in the build.
 
Later,
PW


--
Paul Webster
Hi floor.  Make me a sammich! - GIR

Back to the top