Re: [cross-project-issues-dev] Gerrit ECA check saying I am not a committer

2020-12-09 Thread Wayne Beaton 
The webdev team is working on it.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=569607

The short term work around is to "sign-off-by" your commits.

Wayne

On Wed, Dec 9, 2020 at 9:03 PM Jonah Graham  wrote:

> Hi folks,
>
> Not sure if this is only me, but Gerrit ECA check is reporting me as not a
> committer. I have raised
> https://github.com/EclipseFdn/gerrit-eca-plugin/issues/31
>
> If you are also so affected you can workaround the issue by signing off
> your commits as if you were a contributor.
>
> This problem does not seem to affect stuff once your code is in gerrit,
> just the pushing to gerrit.
>
> Jonah
>
>
> ~~~
> Jonah Graham
> Kichwa Coders
> www.kichwacoders.com
> ___
> 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
>


-- 

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Join us at our virtual event: EclipseCon 2020
 - October 20-22
___
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] Mylyn participation in 2020-12

2020-12-09 Thread Matthias Sohn 
On Thu, Dec 10, 2020 at 2:55 AM Jonah Graham  wrote:

> Hi Matthias / other parties following along,
>
> I think there are two things going on here. In M3 I removed a very small
> part of Mylyn[1], as far as I understood, just the SDK for a part of Mylyn,
> nothing functional. The error message you reported is not caused by that,
> but instead caused by the problem of p2 not taking into consideration
> "uses" directives when doing the upgrade. The error message you get is just
> a more visible problem than was there since 2020-06. In 2020-06 and 2020-09
> at some points within use of Mylyn a user would get failed operation with
> "java.lang.NoClassDefFoundError: javax/xml/bind/JAXBContext" or similar in
> their error log. So in 2020-12 the error has simply been surfaced to happen
> at startup time rather than delayed at runtime.
>
> This error message being visible to everyone doing an upgrade is bad. I
> don't know your exact steps, but got them like this*.
>
> I thought I had mitigated this all properly[2] (i.e. worked around the
> Mylyn bitrotting problem in EPP) by forcing install of the required JAXB
> bundles so that the p2 resolution limitation did not affect the install.
>
> The mitigation done in [2] was supposed to be temporary, i.e until Mylyn
> provided a proper fix! As Mylyn didn't by RC1, I made a slight modification
> to the workaround to make it uninstallable[3]. However, that seems to have
> had the unintended side-effect of causing the upgrade flow to no longer
> upgrade that feature and instead on upgrade that feature is removed from
> the install.
>
> Therefore I will simply revert it [4] and we should be good to go. I have
> tested this locally and will retest tomorrow from the actual build.
>
> There will still be ways to create a bad install, but it should be
> generally harder for users to hit this.
>
> Post-mortem note - this wasn't detected probably because no one tested
> doing an upgrade until you did. I have added an upgrade check to my sanity
> check of releasing.md[5]. Hopefully some of the package maintainers can
> conduct upgrade tests too.
>
>
> * The way I get the error message you have is to start with 2020-09
> committers, add download.eclipse.org/staging/2020-12 as an available
> software site, check for updates and install all updates. On restart I get
> the error you report. However in this case, you get a mismash of upgrades
> and critically you are still running 2020-09 EPP and product. For example
> you get the new PDE, but the old JDT and platform. If you try the same
> steps, but disable all sites except the added staging repo, the upgrade
> will fail with no remedy available error message.
>

yep, I tried the same steps


> As that left me in a different bad state which I don't really consider
> valid I did a check for updates with the following two repos, which are
> pretty close to what the final release repo composite will contain:
> - https://download.eclipse.org/staging/2020-12/
> -
> https://ci.eclipse.org/packaging/job/simrel.epp-tycho-build/lastSuccessfulBuild/artifact/org.eclipse.epp.packages/archive/repository/
> This means that everything upgrades correctly, except the epp.common
> feature as mentioned above. It should work once a build containing [4] is
> built in the next few hours.
>
> [1] https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/172836
> [2] https://www.eclipse.org/lists/epp-dev/msg06089.html
> [3] https://git.eclipse.org/r/c/epp/org.eclipse.epp.packages/+/173324
> [4] https://git.eclipse.org/r/c/epp/org.eclipse.epp.packages/+/173636
> [5]
> https://git.eclipse.org/r/c/epp/org.eclipse.epp.packages/+/173637/1/RELEASING.md
>
> I trust that this will fully resolve the issue until either Mylyn is fixed
> or removed from SimRel. I am very reluctant to remove Mylyn because for the
> people who do like it they really love it and for them it is a big
> differentiator. We need to have a separate discussion about how to save
> Mylyn at some point.
>
> Please let me know your thoughts.
>
> Jonah
>
> ~~~
> Jonah Graham
> Kichwa Coders
> www.kichwacoders.com
>
>
> On Wed, 9 Dec 2020 at 16:55, Matthias Sohn 
> wrote:
>
>> On Wed, Dec 9, 2020 at 10:24 AM Matthias Sohn 
>> wrote:
>>
>>> Currently still some parts of Mylyn's contribution to the simrel 2020-12
>>> are disabled [1].
>>> Will this be fixed soon before RC2 ends ?
>>>
>>> I contributed the JGit/EGit 5.10 release to simrel last night assuming
>>> Mylyn would fix
>>> these disabled parts of its contribution.
>>>
>>> If Mylyn is not able to fix this I have to respin EGit today in order to
>>> remove the EGit Mylyn
>>> integration which depends on org.eclipse.mylyn.commons.sdk.feature.group
>>> which is
>>> currently disabled in simrel.
>>>
>>
>> I got no reaction from Mylyn, neither here nor on [1].
>> Looks like they silently left the simultaneous release :-(
>>
>> I am running out of time to respin EGit today to remove the mylyn related
>> EGit plugins (mylyn and github integration

[cross-project-issues-dev] Gerrit ECA check saying I am not a committer

2020-12-09 Thread Jonah Graham 
Hi folks,

Not sure if this is only me, but Gerrit ECA check is reporting me as not a
committer. I have raised
https://github.com/EclipseFdn/gerrit-eca-plugin/issues/31

If you are also so affected you can workaround the issue by signing off
your commits as if you were a contributor.

This problem does not seem to affect stuff once your code is in gerrit,
just the pushing to gerrit.

Jonah


~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com
___
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] Mylyn participation in 2020-12

2020-12-09 Thread Jonah Graham 
Hi Matthias / other parties following along,

I think there are two things going on here. In M3 I removed a very small
part of Mylyn[1], as far as I understood, just the SDK for a part of Mylyn,
nothing functional. The error message you reported is not caused by that,
but instead caused by the problem of p2 not taking into consideration
"uses" directives when doing the upgrade. The error message you get is just
a more visible problem than was there since 2020-06. In 2020-06 and 2020-09
at some points within use of Mylyn a user would get failed operation with
"java.lang.NoClassDefFoundError: javax/xml/bind/JAXBContext" or similar in
their error log. So in 2020-12 the error has simply been surfaced to happen
at startup time rather than delayed at runtime.

This error message being visible to everyone doing an upgrade is bad. I
don't know your exact steps, but got them like this*.

I thought I had mitigated this all properly[2] (i.e. worked around the
Mylyn bitrotting problem in EPP) by forcing install of the required JAXB
bundles so that the p2 resolution limitation did not affect the install.

The mitigation done in [2] was supposed to be temporary, i.e until Mylyn
provided a proper fix! As Mylyn didn't by RC1, I made a slight modification
to the workaround to make it uninstallable[3]. However, that seems to have
had the unintended side-effect of causing the upgrade flow to no longer
upgrade that feature and instead on upgrade that feature is removed from
the install.

Therefore I will simply revert it [4] and we should be good to go. I have
tested this locally and will retest tomorrow from the actual build.

There will still be ways to create a bad install, but it should be
generally harder for users to hit this.

Post-mortem note - this wasn't detected probably because no one tested
doing an upgrade until you did. I have added an upgrade check to my sanity
check of releasing.md[5]. Hopefully some of the package maintainers can
conduct upgrade tests too.


* The way I get the error message you have is to start with 2020-09
committers, add download.eclipse.org/staging/2020-12 as an available
software site, check for updates and install all updates. On restart I get
the error you report. However in this case, you get a mismash of upgrades
and critically you are still running 2020-09 EPP and product. For example
you get the new PDE, but the old JDT and platform. If you try the same
steps, but disable all sites except the added staging repo, the upgrade
will fail with no remedy available error message.

As that left me in a different bad state which I don't really consider
valid I did a check for updates with the following two repos, which are
pretty close to what the final release repo composite will contain:
- https://download.eclipse.org/staging/2020-12/
-
https://ci.eclipse.org/packaging/job/simrel.epp-tycho-build/lastSuccessfulBuild/artifact/org.eclipse.epp.packages/archive/repository/
This means that everything upgrades correctly, except the epp.common
feature as mentioned above. It should work once a build containing [4] is
built in the next few hours.

[1] https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/172836
[2] https://www.eclipse.org/lists/epp-dev/msg06089.html
[3] https://git.eclipse.org/r/c/epp/org.eclipse.epp.packages/+/173324
[4] https://git.eclipse.org/r/c/epp/org.eclipse.epp.packages/+/173636
[5]
https://git.eclipse.org/r/c/epp/org.eclipse.epp.packages/+/173637/1/RELEASING.md

I trust that this will fully resolve the issue until either Mylyn is fixed
or removed from SimRel. I am very reluctant to remove Mylyn because for the
people who do like it they really love it and for them it is a big
differentiator. We need to have a separate discussion about how to save
Mylyn at some point.

Please let me know your thoughts.

Jonah

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


On Wed, 9 Dec 2020 at 16:55, Matthias Sohn  wrote:

> On Wed, Dec 9, 2020 at 10:24 AM Matthias Sohn 
> wrote:
>
>> Currently still some parts of Mylyn's contribution to the simrel 2020-12
>> are disabled [1].
>> Will this be fixed soon before RC2 ends ?
>>
>> I contributed the JGit/EGit 5.10 release to simrel last night assuming
>> Mylyn would fix
>> these disabled parts of its contribution.
>>
>> If Mylyn is not able to fix this I have to respin EGit today in order to
>> remove the EGit Mylyn
>> integration which depends on org.eclipse.mylyn.commons.sdk.feature.group
>> which is
>> currently disabled in simrel.
>>
>
> I got no reaction from Mylyn, neither here nor on [1].
> Looks like they silently left the simultaneous release :-(
>
> I am running out of time to respin EGit today to remove the mylyn related
> EGit plugins (mylyn and github integrations),
> could do that tomorrow.
>
> I tried upgrading a 2020-09 Committer package with the 5.10 JGit/EGit
> build using the 2020-12 staging repo.
> Upgrade works but afterwards Mylyn views don't load properly complaining
> about the missing disabled features
>

Re: [cross-project-issues-dev] Mylyn participation in 2020-12

2020-12-09 Thread Matthias Sohn 
On Wed, Dec 9, 2020 at 10:24 AM Matthias Sohn 
wrote:

> Currently still some parts of Mylyn's contribution to the simrel 2020-12
> are disabled [1].
> Will this be fixed soon before RC2 ends ?
>
> I contributed the JGit/EGit 5.10 release to simrel last night assuming
> Mylyn would fix
> these disabled parts of its contribution.
>
> If Mylyn is not able to fix this I have to respin EGit today in order to
> remove the EGit Mylyn
> integration which depends on org.eclipse.mylyn.commons.sdk.feature.group
> which is
> currently disabled in simrel.
>

I got no reaction from Mylyn, neither here nor on [1].
Looks like they silently left the simultaneous release :-(

I am running out of time to respin EGit today to remove the mylyn related
EGit plugins (mylyn and github integrations),
could do that tomorrow.

I tried upgrading a 2020-09 Committer package with the 5.10 JGit/EGit build
using the 2020-12 staging repo.
Upgrade works but afterwards Mylyn views don't load properly complaining
about the missing disabled features
and logging the errors [2]. Manual workaround is to first uninstall the
EGit mylyn integration in 2020-09
and then install EGit and JGit 5.10 without the EGit mylyn integration.

I could remove the mylyn and github integrations from simrel immediately
but then upgrade from 2020-09
would probably fail since in 2020-09 these plugins might be installed. So
they would have to be uninstalled manually.
For proper upgrade from older releases we would need to uninstall these
plugins during the upgrade using p2.inf
surgery. This requires implementing this in EGit and respinning the EGit
release which I could tackle tomorrow.

What do you think ?

-Matthias


> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=564699
>

[2] org.osgi.framework.BundleException: Could not resolve module:
org.eclipse.mylyn.github.ui [535]
  Unresolved requirement: Require-Bundle: org.eclipse.mylyn.tasks.ui;
bundle-version="[3.20.0,4.0.0)"
-> Bundle-SymbolicName: org.eclipse.mylyn.tasks.ui;
bundle-version="3.25.2.v20200814-0512"; singleton:="true"
   org.eclipse.mylyn.tasks.ui [331]
 Unresolved requirement: Require-Bundle:
org.eclipse.mylyn.commons.notifications.feed; bundle-version="1.0.0"
   -> Bundle-SymbolicName:
org.eclipse.mylyn.commons.notifications.feed;
bundle-version="1.17.2.v20200813-0821"; singleton:="true"
  org.eclipse.mylyn.commons.notifications.feed [299]
No resolution report for the bundle.  Bundle was not
resolved because of a uses constraint violation.
  org.apache.felix.resolver.reason.ReasonException: Uses constraint
violation. Unable to resolve resource
org.eclipse.mylyn.commons.notifications.feed [osgi.identity;
type="osgi.bundle"; version:Version="1.17.2.v20200813-0821";
osgi.identity="org.eclipse.mylyn.commons.notifications.feed";
singleton:="true"] because it is exposed to package 'javax.xml.bind' from
resources javax.xml.bind [osgi.identity; type="osgi.bundle";
version:Version="2.2.0.v201105210648"; osgi.identity="javax.xml.bind"] and
jakarta.xml.bind [osgi.identity; osgi.identity="jakarta.xml.bind";
type="osgi.bundle"; version:Version="2.3.3.v20201118-1818"] via two
dependency chains.

Chain 1:
  org.eclipse.mylyn.commons.notifications.feed [osgi.identity;
type="osgi.bundle"; version:Version="1.17.2.v20200813-0821";
osgi.identity="org.eclipse.mylyn.commons.notifications.feed";
singleton:="true"]
require: (&(osgi.wiring.bundle=javax.xml.bind)(bundle-version>=2.2.0))
 |
provide: osgi.wiring.bundle: javax.xml.bind
  javax.xml.bind [osgi.identity; type="osgi.bundle";
version:Version="2.2.0.v201105210648"; osgi.identity="javax.xml.bind"]

Chain 2:
  org.eclipse.mylyn.commons.notifications.feed [osgi.identity;
type="osgi.bundle"; version:Version="1.17.2.v20200813-0821";
osgi.identity="org.eclipse.mylyn.commons.notifications.feed";
singleton:="true"]
require: (&(osgi.wiring.bundle=com.sun.xml.bind)(bundle-version>=2.2.0))
 |
provide: osgi.wiring.bundle;
bundle-version:Version="2.3.3.v20201118-1818";
osgi.wiring.bundle="com.sun.xml.bind"
  com.sun.xml.bind [osgi.identity; osgi.identity="com.sun.xml.bind";
type="osgi.bundle"; version:Version="2.3.3.v20201118-1818"]
import:
(&(osgi.wiring.package=javax.xml.bind)(&(version>=2.3.3)(!(version>=2.3.4
 |
export: osgi.wiring.package: javax.xml.bind
  jakarta.xml.bind [osgi.identity; osgi.identity="jakarta.xml.bind";
type="osgi.bundle"; version:Version="2.3.3.v20201118-1818"]
at org.eclipse.osgi.container.Module.start(Module.java:463)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1845)
at
org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1838)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1779)
at
org.eclipse.osgi.containe

Re: [cross-project-issues-dev] Problem with SimRel Validation Builds

2020-12-09 Thread Ed Willink 

Hi

Thanks. I eventually found it after discovering that other contributions 
were progressing.


Just a bit strange for the Validate job to move while the Pipeline job 
didn't.


    Regards

        Ed

On 09/12/2020 09:00, Frederic Gurr wrote:

Hi,

Your Gerrit review was built and merged by the Validate job on the new
SimRel Jiro instance
(https://ci-staging.eclipse.org/simrel/job/simrel.runaggregator.VALIDATE.gerrit/).
So there was no delay and no issue.

To avoid further confusion, I've re-enabled the validate job on the old
JIPP. Until further notice, please disregard
https://ci-staging.eclipse.org/simrel.

Regards,

Fred

On 09.12.20 07:06, Ed Willink wrote:

Hi

The normal
https://ci.eclipse.org/simrel/job/simrel.runaggregator.VALIDATE.gerrit/shows
as disabled since Dec 4th so that just about all RC2 contributions are
blocked. This doesn't seem like waiting till RC2 is done before an infra
change.

How are RC2 contributions supposed top be made?

     Regards

         Ed Willink

On 08/12/2020 09:00, Frederic Gurr wrote:

Hi Jonah,

Thanks for the heads-up and sorry for the noise. The staging repo is
complete, but there was a permissions issue, that made the directories
not readable.

I will make sure that simrel.runaggregator.pipeline runs from the old
instance until RC2 is done.

The migration bug is:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=568118

Regards,

Fred

On 08.12.20 02:50, Jonah Graham wrote:

Hi Fred,

The staging repo is broken. The root files are there, but the
subdirectories (e.g. plugins) are empty. Is the staging-ci version
conflicting with the main ci one? There hasn't been a successful main ci
build since RC2 period started.

A few other things on this subject:

- the ci-staging is triggering EPP builds. I don't think that should
happen until the migration is done.
- the ci-staging seems to be stuck re-running the build despite no
changes. The last few builds all have the same trigger and pair of git
repos.
- the normal ci build seems to be failing in the post build steps only
- is there a bugzilla or similar to subscribe to on the simrel jiro
migration?

Thanks
Jonah



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


On Mon, 7 Dec 2020 at 05:11, Frederic Gurr
mailto:frederic.g...@eclipse-foundation.org>> wrote:

  Hi,

  Sravan is correct. I should have disabled the
  simrel.runaggregator.VALIDATE.gerrit job (which I did on Sunday
after
  the error reports).

  Sorry for the noise.

  Regards,

  Fred

  On 06.12.20 08:30, Sravan K Lakkimsetti wrote:
  > Looks like Fred is migrating Simrel project to JIRO. Please
ignore
  > ci-staging path. This patch did not put a -1 on the gerrit patch
  for me
  > yesterday.
  >
  >
  >
  > Thanks
  >
  > Sravan
  >
  >
  >
  > *From:*Ed Merks mailto:ed.me...@gmail.com>>
  > *Sent:* 06 December 2020 11:13
  > *To:* Cross project issues mailto:cross-project-issues-dev@eclipse.org>>
  > *Subject:* [EXTERNAL] [cross-project-issues-dev] Problem with
SimRel
  > Validation Builds
  >
  >
  >
  > Hi,
  >
  > SimRel validation builds like this are failing:
  >
  >
 
https://ci-staging.eclipse.org/simrel/job/simrel.runaggregator.VALIDATE.gerrit/1904/console


  >
  > I think this is the problem:
  >
  > *06:24:12* No JDK named ‘jdk11-latest’ found
  >
  > Then it uses Java 8:
  >
  > *06:24:24* Java version: 1.8.0_262, vendor: Eclipse OpenJ9,
  runtime: /opt/java/openjdk/jre
  >
  > But Java 8 doesn't work:
  >
  > *06:24:40* Caused by: java.lang.UnsupportedClassVersionError:
  JVMCFRE003 bad major version;
  class=org/eclipse/tycho/extras/eclipserun/EclipseRunMojo, offset=6
  >
  > How did JDK 11 disappear and how do we get it back?
  >
  > I opened the following:
  >
  > https://bugs.eclipse.org/bugs/show_bug.cgi?id=569506
  >
  > 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
  >

  --
  Frederic Gurr
  Release Engineer | Eclipse Foundation Europe GmbH

  Annastr. 46, D-64673 Zwingenberg
  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


__

[cross-project-issues-dev] Mylyn participation in 2020-12

2020-12-09 Thread Matthias Sohn 
Currently still some parts of Mylyn's contribution to the simrel 2020-12
are disabled [1].
Will this be fixed soon before RC2 ends ?

I contributed the JGit/EGit 5.10 release to simrel last night assuming
Mylyn would fix
these disabled parts of its contribution.

If Mylyn is not able to fix this I have to respin EGit today in order to
remove the EGit Mylyn
integration which depends on org.eclipse.mylyn.commons.sdk.feature.group
which is
currently disabled in simrel.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=564699

-Matthias
___
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] Problem with SimRel Validation Builds

2020-12-09 Thread Frederic Gurr 
Hi,

Your Gerrit review was built and merged by the Validate job on the new
SimRel Jiro instance
(https://ci-staging.eclipse.org/simrel/job/simrel.runaggregator.VALIDATE.gerrit/).
So there was no delay and no issue.

To avoid further confusion, I've re-enabled the validate job on the old
JIPP. Until further notice, please disregard
https://ci-staging.eclipse.org/simrel.

Regards,

Fred

On 09.12.20 07:06, Ed Willink wrote:
> Hi
> 
> The normal
> https://ci.eclipse.org/simrel/job/simrel.runaggregator.VALIDATE.gerrit/shows
> as disabled since Dec 4th so that just about all RC2 contributions are
> blocked. This doesn't seem like waiting till RC2 is done before an infra
> change.
> 
> How are RC2 contributions supposed top be made?
> 
>     Regards
> 
>         Ed Willink
> 
> On 08/12/2020 09:00, Frederic Gurr wrote:
>> Hi Jonah,
>>
>> Thanks for the heads-up and sorry for the noise. The staging repo is
>> complete, but there was a permissions issue, that made the directories
>> not readable.
>>
>> I will make sure that simrel.runaggregator.pipeline runs from the old
>> instance until RC2 is done.
>>
>> The migration bug is:
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=568118
>>
>> Regards,
>>
>> Fred
>>
>> On 08.12.20 02:50, Jonah Graham wrote:
>>> Hi Fred,
>>>
>>> The staging repo is broken. The root files are there, but the
>>> subdirectories (e.g. plugins) are empty. Is the staging-ci version
>>> conflicting with the main ci one? There hasn't been a successful main ci
>>> build since RC2 period started.
>>>
>>> A few other things on this subject:
>>>
>>> - the ci-staging is triggering EPP builds. I don't think that should
>>> happen until the migration is done.
>>> - the ci-staging seems to be stuck re-running the build despite no
>>> changes. The last few builds all have the same trigger and pair of git
>>> repos.
>>> - the normal ci build seems to be failing in the post build steps only
>>> - is there a bugzilla or similar to subscribe to on the simrel jiro
>>> migration?
>>>
>>> Thanks
>>> Jonah
>>>
>>>
>>>
>>> ~~~
>>> Jonah Graham
>>> Kichwa Coders
>>> www.kichwacoders.com 
>>>
>>>
>>> On Mon, 7 Dec 2020 at 05:11, Frederic Gurr
>>> >> > wrote:
>>>
>>>  Hi,
>>>
>>>  Sravan is correct. I should have disabled the
>>>  simrel.runaggregator.VALIDATE.gerrit job (which I did on Sunday
>>> after
>>>  the error reports).
>>>
>>>  Sorry for the noise.
>>>
>>>  Regards,
>>>
>>>  Fred
>>>
>>>  On 06.12.20 08:30, Sravan K Lakkimsetti wrote:
>>>  > Looks like Fred is migrating Simrel project to JIRO. Please
>>> ignore
>>>  > ci-staging path. This patch did not put a -1 on the gerrit patch
>>>  for me
>>>  > yesterday.
>>>  >
>>>  >
>>>  >
>>>  > Thanks
>>>  >
>>>  > Sravan
>>>  >
>>>  >
>>>  >
>>>  > *From:*Ed Merks mailto:ed.me...@gmail.com>>
>>>  > *Sent:* 06 December 2020 11:13
>>>  > *To:* Cross project issues >>  >
>>>  > *Subject:* [EXTERNAL] [cross-project-issues-dev] Problem with
>>> SimRel
>>>  > Validation Builds
>>>  >
>>>  >
>>>  >
>>>  > Hi,
>>>  >
>>>  > SimRel validation builds like this are failing:
>>>  >
>>>  >
>>> 
>>> https://ci-staging.eclipse.org/simrel/job/simrel.runaggregator.VALIDATE.gerrit/1904/console
>>>
>>>  >
>>>  > I think this is the problem:
>>>  >
>>>  > *06:24:12* No JDK named ‘jdk11-latest’ found
>>>  >
>>>  > Then it uses Java 8:
>>>  >
>>>  > *06:24:24* Java version: 1.8.0_262, vendor: Eclipse OpenJ9,
>>>  runtime: /opt/java/openjdk/jre
>>>  >
>>>  > But Java 8 doesn't work:
>>>  >
>>>  > *06:24:40* Caused by: java.lang.UnsupportedClassVersionError:
>>>  JVMCFRE003 bad major version;
>>>  class=org/eclipse/tycho/extras/eclipserun/EclipseRunMojo, offset=6
>>>  >
>>>  > How did JDK 11 disappear and how do we get it back?
>>>  >
>>>  > I opened the following:
>>>  >
>>>  > https://bugs.eclipse.org/bugs/show_bug.cgi?id=569506
>>>  >
>>>  > 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
>>>  >
>>>
>>>  --
>>>  Frederic Gurr
>>>  Release Engineer | Eclipse Foundation Europe GmbH
>>>
>>>  Annastr. 46, D-64673 Zwingenberg
>>>  Handelsregister: Darmstadt HRB 92821
>>>  Managing Directors: Gaël Blondelle, Mike Milinkovich
>>>  ___
>>>  cross-project-issues-dev mailing list
>>>  cross-project-iss