Krum,
Thanks for that - I should have just rebased the original change, but wasn't logged into Gerrit so didn't see the option, so here is another change which passes validation:
https://git.eclipse.org/r/#/c/141966/
Do you have power to approve the change?
Andrew
From: "Tsvetkov, Krum" <krum.tsvetkov@xxxxxxx>
To: Memory Analyzer Dev list <mat-dev@xxxxxxxxxxx>
Date: 10/05/2019 12:42
Subject: Re: [mat-dev] 2019-06 simultaneous release
Sent by: mat-dev-bounces@xxxxxxxxxxx
Hi Andrew,
I don’t think the issue has something to do with your changes. I just had a look at some other failed jobs, and the very last one (an update of Eclipse Passage) fails
with exactly the same issue.
There is a discussion on cross-project dev list related to that.
I guess, once the GEF issue is resolved you could rebase the change and give it another try.
Regards,
Krum
From:
<mat-dev-bounces@xxxxxxxxxxx> on behalf of Andrew Johnson
Reply-To: Memory list <mat-dev@xxxxxxxxxxx>
Date: Thursday, 9. May 2019 at 22:34
To: Memory list <mat-dev@xxxxxxxxxxx>
Subject: Re: [mat-dev] 2019-06 simultaneous release
I tried to just touch mat.aggrcon to indicate our participation but got a Gerrit Jenkins build validation error:
https://ci.eclipse.org/simrel/job/simrel.runaggregator.VALIDATE.gerrit/530/
20:46:28 Loading all repositories
20:46:28 Unable to load repository file:/home/data/httpd/download.eclipse.org/tools/gef/updates/milestones/5.0.400M2_gef-master_5261
20:46:30 Unable to load repository p2:file:/home/data/httpd/download.eclipse.org/tools/gef/updates/milestones/5.0.400M2_gef-master_5261
20:46:30 Build failed! Exception was org.eclipse.core.runtime.CoreException: Not all repositories could be loaded (see log for details)
20:46:30 Not all repositories could be loaded (see log for details)
Any ideas?
Andrew
> From: Andrew Johnson
>
> I think we need to do something for the 2019-06 simultaneous release.
>
> https://www.eclipse.org/lists/cross-project-issues-dev/msg16599.html
> >For projects that did participate in the previous simultaneous
> release, the project team's representative must touch the project's
> aggrcon file by the milestone 2 (M2) date of the release to indicate
> that the project wishes to continue participating and that they
> project team is paying attention.
>
> I think we should touch our aggrcon file by Friday and use the
> existing 1.8.1 release. The latest Jenkins build just has a few more
> fixes - for result filtering and the new export HPROF query, which
> might need more testing.
>
> We are still working on the parallel HPROF parsing, but that won't
> be ready for 2019-06, so aim for 2019-09.
>
> Andrew Johnson
>
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
_______________________________________________
mat-dev mailing list
mat-dev@xxxxxxxxxxx
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
