Re: [cross-project-issues-dev] RAP Tools disabled because of conflicts with Eclipse Platform 4.20 M1 contribution

2021-04-16 Thread Frederic Gurr 
On 16.04.21 17:01, Matthias Sohn wrote:
> https://ci.eclipse.org/jetty/job/jetty-rt-bundles-9/ is the job. It
> rebuilds the sources so there is no guarantee that it matches the
> actual Jetty release. In order to be done proper it would have to be
> done like the jetty 10 so actual jetty build artifacts are used and
> to prevent breakages like it can be seen with the multiple Non 27
> builds to wrap up very minimal change exposed by this needless rebuild.
> Note that the job deployment part is broken due to
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=570630 and will need
> fixing too.
> 
> 
> who can provide me permissions to access the configuration of this job ?

Please comment on https://bugs.eclipse.org/bugs/show_bug.cgi?id=572882
and I'll sort it out.

Regards,

Fred


-- 
Frederic Gurr
Release Engineer | Eclipse Foundation Europe GmbH

Berliner Allee 47, D-64295 Darmstadt
Handelsregister: Darmstadt HRB 92821
Managing Directors: Gaël Blondelle, Mike Milinkovich
___
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

Re: [cross-project-issues-dev] RAP Tools disabled because of conflicts with Eclipse Platform 4.20 M1 contribution

2021-04-16 Thread Matthias Sohn 
On Tue, Apr 13, 2021 at 6:21 PM Aleksandar Kurtakov 
wrote:

>
>
> On Tue, Apr 13, 2021 at 7:13 PM Matthias Sohn 
> wrote:
>
>> On Tue, Apr 13, 2021 at 5:42 PM Aleksandar Kurtakov 
>> wrote:
>>
>>>
>>>
>>> On Tue, Apr 13, 2021 at 6:24 PM Nitin Dahyabhai 
>>> wrote:
>>>
 Unfortunately the problem Ed brought up where downstream projects would
 have to reproduce what the Platform does for its Jetty problems is already
 here. WTP needs more Jetty bundles than the Platform provides, and if the
 Platform is using 10.0.1, it would be foolish for me to ship using anything
 else, even 10.0.2.

 I don't know who was taking care of
 https://download.eclipse.org/jetty/updates/jetty-bundles-9.x/, but
 there needs to be something similar for 10.x, and likely 11.x, to serve as
 a canonical p2 repository for all of it. Pulling jars directly from Maven
 seems well suited to products, RCP apps, and configurations that aren't
 expected to be built upon, but for the Platform to use this approach only
 complicates matters. The Platform is an unavoidable middleman in this case.

>>> It was about time for everyone to realize that "The Platform is an
>>> unavoidable middleman in this case." - thanks for stating it that clearly.
>>> We have mostly abandoned our CDT/Linux Tools plugins so we can keep the
>>> Platform running but it's time for others to jump in.
>>> I was the one doing it lately and it was a full rebuild breaking quite
>>> often which I couldn't afford time to redo for 10.x esp with team
>>> shrinking, no one replied to request for help on platform releng and
>>> gaining additional responsibilities. I would welcome anyone stepping up and
>>> doing things in a more general and reusable way - unless/until that happens
>>> I see no other way to keep things but to take the shortest path. There are
>>> simply that many hours in the day and what I or someone else wants doesn't
>>> change the speed of the clock.
>>>
>>
>> if you can point me at how this was done previously with jetty 9.x I may
>> try to care for this.
>> In JGit we are still depending on jetty 9.x since we still want to
>> support Java 8 and we were piggy-backing
>> on the jetty 9.x p2 repos maintained by the platform.
>> I was already wondering where to get a p2 repo for the latest 9.x jetty
>> releases, while platform moved on to jetty 10.7
>>
>
> https://ci.eclipse.org/jetty/job/jetty-rt-bundles-9/ is the job. It
> rebuilds the sources so there is no guarantee that it matches the actual
> Jetty release. In order to be done proper it would have to be done like the
> jetty 10 so actual jetty build artifacts are used and to prevent breakages
> like it can be seen with the multiple Non 27 builds to wrap up very minimal
> change exposed by this needless rebuild.
> Note that the job deployment part is broken due to
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=570630 and will need fixing
> too.
>

who can provide me permissions to access the configuration of this job ?


>
>
>>
>> I am not listening on the platform releng list, that's why I didn't see
>> your request for help.
>>
>>
>>>
 --
 Regards,
 Nitin Dahyabhai
 Eclipse WTP PMC
 ___
 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

>>>
>>>
>>> --
>>> Aleksandar Kurtakov
>>> Red Hat Eclipse Team
>>> ___
>>> 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
>>
>
>
> --
> Aleksandar Kurtakov
> Red Hat Eclipse Team
> ___
> 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

Re: [cross-project-issues-dev] SimRel 2021-06 Milestone 1 (M1) is available

2021-04-16 Thread Frederic Gurr 
Hence my vague wording "will be available soon". ;)

On 16.04.21 16:09, Ed Merks wrote:
> Fred,
> 
> The page https://www.eclipse.org/downloads/packages/release/2021-06/m1
> is there but it appears to have major "php" issues.
> 
> Regards,
> Ed
> 
> On 16.04.2021 16:03, Frederic Gurr wrote:
>> Hi,
>>
>> The 2021-06 M1 update repository is now available from:
>>
>> => http://download.eclipse.org/releases/2021-06/
>>
>> The EPP Packages will be available soon:
>>
>> => https://www.eclipse.org/downloads/packages/release/2021-06/m1
>>
>> Thanks everyone for participating!
>>
>>
>> Regards,
>>
>> Fred
>>
> ___
> 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

-- 
Frederic Gurr
Release Engineer | Eclipse Foundation Europe GmbH

Berliner Allee 47, D-64295 Darmstadt
Handelsregister: Darmstadt HRB 92821
Managing Directors: Gaël Blondelle, Mike Milinkovich
___
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

Re: [cross-project-issues-dev] SimRel 2021-06 Milestone 1 (M1) is available

2021-04-16 Thread Jonah Graham 
I think the php issues are now resolved. I suspect the issue is the timing
of Eric's work - he just posted to epp-dev that the page is ready.

Jonah


~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Fri, 16 Apr 2021 at 10:09, Ed Merks  wrote:

> Fred,
>
> The page https://www.eclipse.org/downloads/packages/release/2021-06/m1
> is there but it appears to have major "php" issues.
>
> Regards,
> Ed
>
> On 16.04.2021 16:03, Frederic Gurr wrote:
> > Hi,
> >
> > The 2021-06 M1 update repository is now available from:
> >
> > => http://download.eclipse.org/releases/2021-06/
> >
> > The EPP Packages will be available soon:
> >
> > => https://www.eclipse.org/downloads/packages/release/2021-06/m1
> >
> > Thanks everyone for participating!
> >
> >
> > Regards,
> >
> > Fred
> >
> ___
> 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

Re: [cross-project-issues-dev] SimRel 2021-06 Milestone 1 (M1) is available

2021-04-16 Thread Ed Merks 

Fred,

The page https://www.eclipse.org/downloads/packages/release/2021-06/m1 
is there but it appears to have major "php" issues.


Regards,
Ed

On 16.04.2021 16:03, Frederic Gurr wrote:

Hi,

The 2021-06 M1 update repository is now available from:

=> http://download.eclipse.org/releases/2021-06/

The EPP Packages will be available soon:

=> https://www.eclipse.org/downloads/packages/release/2021-06/m1

Thanks everyone for participating!


Regards,

Fred


___
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] SimRel 2021-06 Milestone 1 (M1) is available

2021-04-16 Thread Frederic Gurr 
Hi,

The 2021-06 M1 update repository is now available from:

=> http://download.eclipse.org/releases/2021-06/

The EPP Packages will be available soon:

=> https://www.eclipse.org/downloads/packages/release/2021-06/m1

Thanks everyone for participating!


Regards,

Fred

-- 
Frederic Gurr
Release Engineer | Eclipse Foundation Europe GmbH

Berliner Allee 47, D-64295 Darmstadt
Handelsregister: Darmstadt HRB 92821
Managing Directors: Gaël Blondelle, Mike Milinkovich
___
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

Re: [cross-project-issues-dev] SWT win32 Broken in Latest 4.20 IBuild?

2021-04-16 Thread Ed Merks 

Niraj and Sravan,

Many thanks!  I am very impressed with the helpful and extremely speedy 
resolution of this problem!!


Regards,
Ed

On 16.04.2021 14:35, Niraj Modi wrote:

Hi All,
Windows Signing service is working now, fixed via***Bug 572896* 
 and related 
*Bug 572911* 

Fresh Eclipse IBuild is in progress now:
I20210416-0810
Regards,
Niraj Modi

- Original message -
From: Niraj Modi/India/IBM
To: Sravan K Lakkimsetti/India/IBM@IBM
Cc: cross-project-issues-dev@eclipse.org
Subject: RE: [EXTERNAL] [cross-project-issues-dev] SWT win32
Broken in Latest 4.20 IBuild?
Date: Fri, Apr 16, 2021 12:15 PM
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*
 - Windows
Signing service is down or link broken
Regards,
Niraj Modi

- Original message -
From: Sravan K Lakkimsetti/India/IBM
To: "Cross project issues"
, 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 
Sent: 16 April 2021 11:18
To: Cross project issues 
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
___
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

Re: [cross-project-issues-dev] SWT win32 Broken in Latest 4.20 IBuild?

2021-04-16 Thread Niraj Modi 
Hi All,
Windows Signing service is working now, fixed via Bug 572896 and related Bug 572911
Fresh Eclipse IBuild is in progress now:
I20210416-0810
 
Regards,
Niraj Modi
- Original message -From: Niraj Modi/India/IBMTo: Sravan K Lakkimsetti/India/IBM@IBMCc: cross-project-issues-dev@eclipse.orgSubject: RE: [EXTERNAL] [cross-project-issues-dev] SWT win32 Broken in Latest 4.20 IBuild?Date: Fri, Apr 16, 2021 12:15 PM 
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  - Windows Signing service is down or link broken 
 
Regards,
Niraj Modi
- Original message -From: Sravan K Lakkimsetti/India/IBMTo: "Cross project issues" , Niraj Modi/India/IBM@IBMCc: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=a26b79c959e884b3a3a96ce2e2cbf0b6ef9e6d23Need to investigate why this happened.@Niraj ModiCan you please help?ThanksSravan-Original Message-From: Ed Merks  Sent: 16 April 2021 11:18To: Cross project issues Subject: [EXTERNAL] [cross-project-issues-dev] SWT win32 Broken in Latest 4.20 IBuild?Hi,I updated my target platform fromhttp://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 applicationUsing 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 listcross-project-issues-dev@eclipse.orgTo 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

Re: [cross-project-issues-dev] SWT win32 Broken in Latest 4.20 IBuild?

2021-04-16 Thread Sopot Cela 
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  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  
> *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 
> 
>
> 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*  -
> Windows Signing service is down or link broken
>
>
>
> Regards,
>
> Niraj Modi
>
> - Original message -
> From: Sravan K Lakkimsetti/India/IBM
> To: "Cross project issues" 
> , 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
>

Re: [cross-project-issues-dev] SWT win32 Broken in Latest 4.20 IBuild?

2021-04-16 Thread Ed Willink 

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 
*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  


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*
 - Windows
Signing service is down or link broken

Regards,

Niraj Modi

- Original message -
From: Sravan K Lakkimsetti/India/IBM
To: "Cross project issues"

, 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

Re: [cross-project-issues-dev] SWT win32 Broken in Latest 4.20 IBuild?

2021-04-16 Thread Sravan K Lakkimsetti 
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  
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 

 

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 - Windows 
Signing service is down or link broken 

 

Regards,

Niraj Modi

- Original message -
From: Sravan K Lakkimsetti/India/IBM
To: "Cross project issues"   
, 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    
Sent: 16 April 2021 11:18
To: Cross project issues   

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

Re: [cross-project-issues-dev] SWT win32 Broken in Latest 4.20 IBuild?

2021-04-16 Thread Ed Willink 

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  


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*  - 
Windows Signing service is down or link broken

Regards,
Niraj Modi

- Original message -
From: Sravan K Lakkimsetti/India/IBM
To: "Cross project issues" ,
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 
Sent: 16 April 2021 11:18
To: Cross project issues 
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



--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
___
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

Re: [cross-project-issues-dev] SWT win32 Broken in Latest 4.20 IBuild?

2021-04-16 Thread Niraj Modi 
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  - Windows Signing service is down or link broken 
 
Regards,
Niraj Modi
- Original message -From: Sravan K Lakkimsetti/India/IBMTo: "Cross project issues" , Niraj Modi/India/IBM@IBMCc: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=a26b79c959e884b3a3a96ce2e2cbf0b6ef9e6d23Need to investigate why this happened.@Niraj ModiCan you please help?ThanksSravan-Original Message-From: Ed Merks  Sent: 16 April 2021 11:18To: Cross project issues Subject: [EXTERNAL] [cross-project-issues-dev] SWT win32 Broken in Latest 4.20 IBuild?Hi,I updated my target platform fromhttp://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 applicationUsing 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 listcross-project-issues-dev@eclipse.orgTo 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

Re: [cross-project-issues-dev] SWT win32 Broken in Latest 4.20 IBuild?

2021-04-16 Thread Rolf Theunissen 
It seemed like the signing service was having trouble, from the commit
message:

diff --git
a/bundles/org.eclipse.swt.win32.win32.x86_64/swt-gdip-win32-4944r16.dll
b/bundles/org.eclipse.swt.win32.win32.x86_64/swt-gdip-win32-4944r16.dll
new file mode 100644
index 0..0ab5323f8
--- /dev/null
+++ b/bundles/org.eclipse.swt.win32.win32.x86_64/swt-gdip-win32-4944r16.dll

@@ -0,0 +1,3 @@
+HTTP Error 400
+Problem accessing '/authenticode/sign'
+Reason: Bad Request

Op vr 16 apr. 2021 om 08:16 schreef Sravan K Lakkimsetti <
sravankum...@in.ibm.com>:

> 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 
> Sent: 16 April 2021 11:18
> To: Cross project issues 
> 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
>
___
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

Re: [cross-project-issues-dev] SWT win32 Broken in Latest 4.20 IBuild?

2021-04-16 Thread Sravan K Lakkimsetti 


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 
Sent: 16 April 2021 11:18
To: Cross project issues 
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