Hi Ed, Just wanted to say that the tone in which you ask questions in this thread, and the tone in which you address your reply to Sravan is quite insufferable. The flood of question marks and exclamation marks is quite childish and really doesn't help. Nobody here owes you (as in personally) anything.
Thanks Niraj for filing the bug and Sravan for following up. Sopot On Fri, Apr 16, 2021 at 10:29 AM Ed Willink <ed.will...@gmail.com> wrote: > Hi > > I don't understand. Many (?all) projects have discovered that the > increased EF integrity makes it really hard to promote from the Jenkins > build area to the public downloads area. Consequently my builds, when > successful, trigger a separate promotion job. Nothing gets promoted till > the build succeeds. Surely the platform should keep candidates in the > Jenkins workspace or some private project space until such time as the > analysis has confirmed that they are fit for public consumption? Users who > really want an unstable build can download from the private workspace. > Promoting then analysing then marking as unstable seems like a recipe for > confused users. > > "often they'll see a good build" !!! Surely must be always? You haven't > explained how Tycho magically took the oldest of three (all stable) and so > happened to allow the OCL build to succeed. > > You haven't explained how a not-unstable build has over 7000 fails. > > You haven't explained why any not-unstable builds has any fails at all. > > Regards > > Ed Willink > On 16/04/2021 08:41, Sravan K Lakkimsetti wrote: > > Hi Ed, > > > > Here is the process we follow, > > > > There are two steps in promotion. > > 1. Promote build to downloads pages. To serve users who want to > download. > 2. Add to I-builds composite repository > > > > When we find problems with build we mark a build as unstable. This removes > offending build from I-builds composite repository. This enables end users > to use a good build for upgrade process. These broken builds stay for a > week on the download page and after they are automatically removed. This > process is there for developers to analyse problems. > > > > Due to this process whenever downstream projects point to I-builds > composite most often they’ll see a good build. We also mark a build > unstable if we find any problems during the build process itself. > > > > Because of above mentioned process Tycho will not pull a bad build in > maximum cases. > > > > Hope this explanation helps > > > > Thanks > > Sravan > > > > *From:* Ed Willink <ed.will...@gmail.com> <ed.will...@gmail.com> > *Sent:* 16 April 2021 12:36 > *To:* cross-project-issues-dev@eclipse.org > *Subject:* [EXTERNAL] Re: [cross-project-issues-dev] SWT win32 Broken in > Latest 4.20 IBuild? > > > > Hi > > There is something much stranger gong on. > > I ran an early OCL build that would have run on Sunday. It has SWT usage > but the build runs fine, because it used > > https://download.eclipse.org/eclipse/updates/4.20-I-builds/I20210413-1400 > <https://download.eclipse.org/eclipse/updates/4.20-I-builds/I20210413-1400/plugins/> > > although that is the earliest of the 3 listed in the > compositeArtifacts.jar. If it had used the more recent then the problem > might have shown up. > > ?? Why did Tycho fail to pull in the broken build ?? > > http://download.eclipse.org/eclipse/downloads/drops4/I20210413-1400/ has > 63 test fails which is rather disturbing. > > http://download.eclipse.org/eclipse/downloads/drops4/I20210415-0010/, > which is not marked as unstable, has 7057 fails. > > Surely such a high number of fails should be a private matter to be > resolved by the platform committers with no more trouble to the community > as a whole than perhaps a polite message to cross-project-dev announcing > the lack of build promotions while a problem is investigated. > > Why does http://download.eclipse.org/eclipse/downloads/ show unstable > builds? Surely these too should not have been promoted to waste disc space > / confuse the community? > > Why do any builds have any fails at all? Surely a test that fails is a > test that fails? In my code, if a test is proving problematic then I raise > a Bugzilla and comment out the test until a solution is found. > > Regards > > Ed Willink > > > > > > On 16/04/2021 07:45, Niraj Modi wrote: > > Hi All, > > We learned that Windows Signing service is down/broken: > http://build.eclipse.org:31338/winsign.php > > > > Raised a blocker below bug with Eclipse foundation: > > *Bug 572896* <https://bugs.eclipse.org/bugs/show_bug.cgi?id=572896> - > Windows Signing service is down or link broken > > > > Regards, > > Niraj Modi > > ----- Original message ----- > From: Sravan K Lakkimsetti/India/IBM > To: "Cross project issues" <cross-project-issues-dev@eclipse.org> > <cross-project-issues-dev@eclipse.org>, Niraj Modi/India/IBM@IBM > Cc: > Subject: RE: [EXTERNAL] [cross-project-issues-dev] SWT win32 Broken in > Latest 4.20 IBuild? > Date: Fri, Apr 16, 2021 11:46 AM > > Found the faulty commit > https://git.eclipse.org/c/platform/eclipse.platform.swt.binaries.git/commit/?id=a26b79c959e884b3a3a96ce2e2cbf0b6ef9e6d23 > > Need to investigate why this happened. > > @Niraj Modi > Can you please help? > > Thanks > Sravan > > -----Original Message----- > From: Ed Merks <ed.me...@gmail.com> <ed.me...@gmail.com> > Sent: 16 April 2021 11:18 > To: Cross project issues <cross-project-issues-dev@eclipse.org> > <cross-project-issues-dev@eclipse.org> > Subject: [EXTERNAL] [cross-project-issues-dev] SWT win32 Broken in Latest > 4.20 IBuild? > > Hi, > > I updated my target platform from > http://download.eclipse.org/eclipse/updates/4.20-I-builds and after that > I could not run any SWT applications anymore: > > java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: > > > D:\Users\merks\oomph-1.21\ws\.metadata\.plugins\org.eclipse.pde.core\IDE\org.eclipse.osgi\480\0\.cp\swt-win32-4944r16.dll: > %1 is not a valid Win32 application > no swt-win32 in java.library.path: [C:\Program > Files\Java\jdk-11.0.9\bin,....] > D:\Users\merks\.swt\lib\win32\x86_64\swt-win32-4944r16.dll: %1 is not > a valid Win32 application > Can't load library: D:\Users\merks\.swt\lib\win32\x86_64\swt-win32.dll > D:\Users\merks\.swt\lib\win32\x86_64\swt-win32-4944r16.dll: %1 is not > a valid Win32 application > > Using http://download.eclipse.org/releases/2021-06/202104161000 instead > works fine, so it seems to be something that's happened between M1 and > today. > > Has anyone else noticed this? For those who "eat our own dog food", such > a problem could cripple your IDE if you update the IDE itself... > > Regards, > Ed > > > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev > > > > > > > _______________________________________________ > > cross-project-issues-dev mailing list > > cross-project-issues-dev@eclipse.org > > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev > > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > > Virus-free. www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > > > > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev > -- Sopot Cela Software Engineering Manager <https://red.ht/sig>
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
