Community
Participate
Working Groups
Source code tags are not generated for both M-build and I-build. This needs to be fixed as soon as possible.
Here is the specific error message I am seeing in the log 08:08:38 Entering 'eclipse.jdt' 08:08:38 Pushing to file:///gitroot/jdt/eclipse.jdt 08:08:39 remote: Can't locate Net/LDAP.pm in @INC (you may need to install the Net::LDAP module) (@INC contains: /usr/lib/perl5/site_perl/5.18.2/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.18.2 /usr/lib/perl5/vendor_perl/5.18.2/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.18.2 /usr/lib/perl5/5.18.2/x86_64-linux-thread-multi /usr/lib/perl5/5.18.2 /usr/lib/perl5/site_perl .) at /home/data/common/eclipse.org-common-ldap.pl line 22. 08:08:39 remote: BEGIN failed--compilation aborted at /home/data/common/eclipse.org-common-ldap.pl line 22. 08:08:39 remote: Compilation failed in require at hooks/update line 5. 08:08:39 remote: error: hook declined to update refs/tags/I20160629-0800 08:08:39 To file:///gitroot/jdt/eclipse.jdt 08:08:39 ! [remote rejected] I20160629-0800 -> I20160629-0800 (hook declined) 08:08:39 error: failed to push some refs to 'file:///gitroot/jdt/eclipse.jdt'
There are a lot of comparator errors in the I build. I think this is related to tagging. http://download.eclipse.org/eclipse/downloads/drops4/I20160629-0800/buildlogs/comparatorlogs/buildtimeComparatorUnanticipated.log.txt
(In reply to Sravan Kumar Lakkimsetti from comment #1) > 08:08:38 Pushing to file:///gitroot/jdt/eclipse.jdt I think the problem is that this repo doesn't exist on the filesystem. Correct url would be: file:///gitroot/jdt/eclipse.jdt.git ^^^^ needs ".git" Bug 496335 comment 20 says this push was successful, and this includes ".git": > Pushing to file:///gitroot/platform/eclipse.platform.releng.aggregator.git
(In reply to Markus Keller from comment #3) That was probably a red herring. https://hudson.eclipse.org/releng/job/I-build/lastBuild/consoleText says it successfully ran ... > Pushing to file:///gitroot/platform/eclipse.platform.common ... but it failed for ... > Pushing to file:///gitroot/platform/eclipse.platform The difference is that the eclipse.platform.common repo does NOT have a hooks/update file, so the perl script that fails in other repos doesn't actually run. eclipse.platform.releng.aggregator.git also misses the hooks/update script. I'll update bug 496335.
after updating the LDAP module still not able to tag the repos. Here is the error message we are getting 16:06:01 Entering 'eclipse.jdt' 16:06:01 Pushing to file:///gitroot/jdt/eclipse.jdt 16:06:01 fatal: Unable to create '/home/data/git/jdt/eclipse.jdt.git/refs/tags/I20160705-1600.lock': Permission denied 16:06:01 fatal: The remote end hung up unexpectedly 16:06:01 fatal: The remote end hung up unexpectedly Tags got created for equinox bundles but not created for platform bundles. Looks like permission issue on platform bundles
@David I am now how git repo will behave after changing permissions. I suggest recreating the bare-repo using genie.releng id.
@David I am not sure how git repo will behave after changing permissions. I suggest recreating the bare-repo using genie.releng id.
I did some analysis on this. looking at http://build.eclipse.org/eclipse/builds/4I/gitCache/eclipse.platform.releng.aggregator/rt.equinox.framework/bundles/org.eclipse.osgi/target/.apibuild.xml I found <apitooling.apigeneration projectname="org.eclipse.osgi_3.11.100.v20160630-1447" Here the qualifier mentioned here for release version. I checked qualifier for this package in 4.6 release it is different. I think it is problem with the qualifier. The qualifier v20160630-1447 is for June30th build. But we did not had any build on that day(N-build qualifier stats with N). From where this one came?
(In reply to Sravan Kumar Lakkimsetti from comment #6) > @David > > I am now how git repo will behave after changing permissions. I suggest > recreating the bare-repo using genie.releng id. We dont't need the bare repo recreated ... assuming you mean the one on eclipse.org. This "permission problem" is all do to ldap permissions granted to the genie.releng user. In come cases, we might need to reclone the build directory, but so far it has done fine. Let me know if the difference between those two (or what I am talking about is not clear).
(In reply to David Williams from comment #9) > (In reply to Sravan Kumar Lakkimsetti from comment #6) > > @David > > > > I am now how git repo will behave after changing permissions. I suggest > > recreating the bare-repo using genie.releng id. > > We dont't need the bare repo recreated ... assuming you mean the one on > eclipse.org. > > This "permission problem" is all do to ldap permissions granted to the > genie.releng user. > > In come cases, we might need to reclone the build directory, but so far it > has done fine. > > Let me know if the difference between those two (or what I am talking about > is not clear). What I mean is the bare repo on the build machine. which we access using file:///gitroot. I think we may not need this this is the error message we are getting fatal: Unable to create '/home/data/git/jdt/eclipse.jdt.git/refs/tags/I20160705-1600.lock': Permission denied. ther are two sets of permissions one with git level and another at unix permissions. To elimeinate the problem with unix level can you try to create a file at that location?
It is a mystery to me that the push to the rt.equinox.bundles repo succeeded but the push to eclipse.platform.ui failed. getfacl returns pretty similar access rights when I check from build.eclipse.org. Maybe check the access right from the releng hudson job? Could be that that machine has a different user <-> id mapping. (In reply to Sravan Kumar Lakkimsetti from comment #8) > The qualifier v20160630-1447 is for June30th build. But we did not had any > build on that day(N-build qualifier stats with N). From where this one came? Bundle qualifiers are generated based on the timestamp of the HEAD commit, not based on the time when the build ran.
Should be good to go after the server restart in bug 496335 . Sheesh!
