[cross-project-issues-dev] "Aggregation model is inconsistent" errors

[David M Williams]

If I've said it N times, I've said it N+1 times, if you change 
"categories" or change "contacts" you need to use the b3 aggegator editor, 
and make the changes using the "model editor". The reason is these changes 
make changes in two files, the "main" one, "simrel.b3aggr", and your 
individual ".b3aggrcon" file -- and then both files need to be 
committed/pushed. 

As of right now, the 'head' of the model is breaking due to invalid 
"categories" and the "Gerrit job" is breaking due to invalid "contacts". 

I have not looked, yet, for "who did what", but thought I'd send this 
blanket reminder, and perhaps by the time I wake up, it will be all fixed. 
:) 

If not, I will "slash and burn" to make the model valid, and/or completely 
revert changes that broke the model, if I can tell. That is, I will not be 
able to "fix correctly" since I do not know what was intended. 

If anyone needs specific help, please open a cross-project bug asking for 
it and stating what you intend to accomplish. Thanks. 

Hope this reminder helps, 


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] "Aggregation model is inconsistent" errors

[Mickael Istria]

On 12/16/2015 09:39 AM, David M Williams wrote:
As of right now, the 'head' of the model is breaking due to invalid 
"categories" and the "Gerrit job" is breaking due to invalid "contacts".

@David:
As far as I can see, the failing Gerrit job is a good thing, since it 
did vote -1 on an ongoing review, and it helped the other to fix their 
contribution before they could merge it.
Where is the CI job highlighting that HEAD is breaking? I'm on 
https://hudson.eclipse.org/simrel/job/simrel.neon.runaggregator.BUILD__CLEAN/ 
and everything is green.


@All:
Like many are already doing, even if you're a SimRel committer and if 
you're using the simrel model editor, it's always a good idea to take 
advantage of the validation step offered by Gerrit: 
https://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build#Contribute_via_a_Gerrit_review 
. When pushing to Gerrit, the model is automatically validated and you 
get a -1 when the model is broken (because of your change, or an earlier 
one on your branch but that 2nd case isn't frequent), then you can amend 
your patch and submit it again until you get a +1 and permission to 
merge via Gerrit if everything seems good. This workflow prevents from 
breaking "production" branches.

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat 
My blog  - My Tweets 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Disk usage report for Hudson/Build

[genie]

Compiled 2015-12-16T12:07

 build.eclipse.org 
-> Usage exceeding 1GB for: Hudson master jobs and workspace (2015-12-16T10:00)
   2.8G papyrus-trunk-nightly
   1.7G papyrus-trunk-extra-nightly
   1.6G emf-cdo-integration
-> Usage exceeding 1GB for: /shared (1000G capacity) (2015-12-16T10:00)
 466.1G hipp
 166.3G rt
 118.5G eclipse
  36.5G webtools
  34.4G technology
  23.1G SLES
  20.0G common
  12.0G tools
   9.8G jobs
   6.7G cbi-ng
   5.7G orbit
   5.3G modeling
   4.9G simrel
   1.6G mylyn
   1.5G cbi
   1.4G soa
-> Usage exceeding 1GB for: /shared/modeling
   3.1G build
-> Usage exceeding 1GB for: /shared/tools
   4.6G tm
   3.1G objectteams
   1.4G mtj
   1.1G aspectj
-> Usage exceeding 1GB for: /shared/technology
  18.6G epp
   4.8G stem
   4.5G babel
   2.4G cosmos
   1.6G m2e
 END: build.eclipse.org 


 hudson-slave1.eclipse.org 
/dev/xvda1158G   24G  134G  16% /
-> Usage exceeding 1GB for: Hudson workspace on hudson-slave1 (50G capacity) 
(2015-12-15T21:00)
 END: hudson-slave1.eclipse.org 


 hudson-slave2.eclipse.org 
-> Usage exceeding 1GB for: 
 END: hudson-slave2.eclipse.org 


 hudson-slave3.eclipse.org 
/dev/xvda1 55G   23G   33G  41% /
-> Usage exceeding 1GB for: Hudson workspace on hudson-slave3 (50G capacity) 
(2015-12-15T18:00)
 END: hudson-slave3.eclipse.org 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Mac signing service issues

[Denis Roy]

Folks,

The Mac signing service is currently broken. We're tracking the issue in :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=484438

Denis

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Oomph's M4 may be late

[Eike Stepper]

Hi,

I just wanted to let you know that Oomph's M4 may be late today because of 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=484438


Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Mac signing service issues -- plan for M4

[David M Williams]

Given there is currently "no solution in sight" for this week, I think the 
best course of action is to push ahead, and produce M4 as planned, with 
affected projects disabling "Mac signing". 

Once we have that build "in hand", a) if the user experience is "really 
bad", we can reconsider (but as far as know, if they are doing fresh 
install, then they have to do that "open" or "ctrl-open" trick we have 
used in the past -- that is, in the past there has been milestones without 
a Mac signature. b) if enough people are around next week, to redo 
contributions with Mac signed, we can do an M4a deliverable. 

But, in either case, since we are between a rock and a hard place, I think 
best to try and produce one as planned. Otherwise, we might be well into 
January before we could produce one, depending on everyone's holiday 
schedules. 

Thanks, 





From:   Denis Roy 
To: Cross project issues , 
Date:   12/16/2015 01:36 PM
Subject:[cross-project-issues-dev] Mac signing service issues
Sent by:cross-project-issues-dev-boun...@eclipse.org



Folks,

The Mac signing service is currently broken. We're tracking the issue in :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=484438

Denis

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev




___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Data Tools Platform (DTP) project participation in Eclipse Neon

[Brian Payton]

The Data Tools Platform (DTP) project will participate in the Neon 
simultaneous release with an offset of +1. 

We plan to contribute the 1.13.0 version of DTP: 
https://projects.eclipse.org/projects/datatools/releases/1.13.0

Regards,
Brian

Brian Payton
DTP PMC Lead
Developer Tooling for Data Services
IBM Silicon Valley Laboratory



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Oomph's M4 may be late

[Eike Stepper]

Am 16.12.2015 um 20:01 schrieb Eike Stepper:

Hi,

I just wanted to let you know that Oomph's M4 may be late today because of 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=484438

Sorry, Oomph won't contribute an M4.

Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper




Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev




___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] "Aggregation model is inconsistent" errors

[David M Williams]

Michael, Yes, I agree that "if you are going to fail a build, a Gerrit 
build it the best kind to fail" ... but, still, I wouldn't exactly call it 
a "good thing" when someone makes an all too common of an error. 
But, I indeed would not have to "revert" anything in that case, and that 
*is* a good thing. :) 

As for the "categories". I was basing my statement on my "local run" in 
the b3 aggegator editor and I think I must have something wrong with my 
install, so I will try to fix that up today to avoid future false alarms. 

Thanks, 



From:   Mickael Istria 
To: cross-project-issues-dev@eclipse.org, 
Date:   12/16/2015 04:02 AM
Subject:Re: [cross-project-issues-dev] "Aggregation model is 
inconsistent" errors
Sent by:cross-project-issues-dev-boun...@eclipse.org



On 12/16/2015 09:39 AM, David M Williams wrote:
As of right now, the 'head' of the model is breaking due to invalid 
"categories" and the "Gerrit job" is breaking due to invalid "contacts". 
@David:
As far as I can see, the failing Gerrit job is a good thing, since it did 
vote -1 on an ongoing review, and it helped the other to fix their 
contribution before they could merge it.
Where is the CI job highlighting that HEAD is breaking? I'm on 
https://hudson.eclipse.org/simrel/job/simrel.neon.runaggregator.BUILD__CLEAN/ 
and everything is green.

@All:
Like many are already doing, even if you're a SimRel committer and if 
you're using the simrel model editor, it's always a good idea to take 
advantage of the validation step offered by Gerrit: 
https://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build#Contribute_via_a_Gerrit_review
 
. When pushing to Gerrit, the model is automatically validated and you get 
a -1 when the model is broken (because of your change, or an earlier one 
on your branch but that 2nd case isn't frequent), then you can amend your 
patch and submit it again until you get a +1 and permission to merge via 
Gerrit if everything seems good. This workflow prevents from breaking 
"production" branches.
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Oomph's M4 may be late

[David M Williams]

Eike, care to elaborate? Are there technical reasons I am not aware of? Or 
is it that you just don't want to bother, if the infrastructure is not 
working? 

I assume your M3 version (which is what is currently "in the repo") will 
still "work" with the rest of the stack at M4? 

Thanks, 




From:   Eike Stepper 
To: cross-project-issues-dev@eclipse.org, 
Date:   12/16/2015 05:30 PM
Subject:Re: [cross-project-issues-dev] Oomph's M4 may be late
Sent by:cross-project-issues-dev-boun...@eclipse.org



Am 16.12.2015 um 20:01 schrieb Eike Stepper:
> Hi,
>
> I just wanted to let you know that Oomph's M4 may be late today because 
of 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=484438
Sorry, Oomph won't contribute an M4.

Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


>
> Cheers
> /Eike
>
> 
> http://www.esc-net.de
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
>
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev




___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] "Aggregation model is inconsistent"errors

[David M Williams]

Ah, I'm glad this message finally came through ... it all depends on the 
"luck of the queue" or something. 

BUT, I have reinstalled, and even re-cloned, and still seeing the same 
problem with 'categories' in the b3 editor. Does anyone else? If I select 
the "validate" action it shows me there are several features in the 
Modeling Category that are "un-referenced" (or something like that). There 
is about 8 total. I'm not sure if features were attempted to be removed 
from the Modeling category? Or if some were being added? 

In any case, Modeling projects should be sure to take a look at "staging" 
repo, to make sure all is as intended. I think "everything is in" the 
repository, and this is just a category issue, since if I pick "validate 
aggregation" it passes OK. 

I have opened bug 484518[1] to track the difference in "results" between 
various forms of 'validate'. 

Thanks

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





From:   David M Williams/Raleigh/IBM@IBMUS
To: Cross project issues , 
Date:   12/16/2015 05:52 PM
Subject:Re: [cross-project-issues-dev] "Aggregation model is 
inconsistent"   errors
Sent by:cross-project-issues-dev-boun...@eclipse.org



Michael, Yes, I agree that "if you are going to fail a build, a Gerrit 
build it the best kind to fail" ... but, still, I wouldn't exactly call it 
a "good thing" when someone makes an all too common of an error. 
But, I indeed would not have to "revert" anything in that case, and that 
*is* a good thing. :) 

As for the "categories". I was basing my statement on my "local run" in 
the b3 aggegator editor and I think I must have something wrong with my 
install, so I will try to fix that up today to avoid future false alarms. 

Thanks, 



From:Mickael Istria 
To:cross-project-issues-dev@eclipse.org, 
Date:12/16/2015 04:02 AM
Subject:Re: [cross-project-issues-dev] "Aggregation model is 
inconsistent" errors
Sent by:cross-project-issues-dev-boun...@eclipse.org



On 12/16/2015 09:39 AM, David M Williams wrote:
As of right now, the 'head' of the model is breaking due to invalid 
"categories" and the "Gerrit job" is breaking due to invalid "contacts". 
@David:
As far as I can see, the failing Gerrit job is a good thing, since it did 
vote -1 on an ongoing review, and it helped the other to fix their 
contribution before they could merge it.
Where is the CI job highlighting that HEAD is breaking? I'm on 
https://hudson.eclipse.org/simrel/job/simrel.neon.runaggregator.BUILD__CLEAN/
and everything is green.

@All:
Like many are already doing, even if you're a SimRel committer and if 
you're using the simrel model editor, it's always a good idea to take 
advantage of the validation step offered by Gerrit: 
https://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build#Contribute_via_a_Gerrit_review
. When pushing to Gerrit, the model is automatically validated and you get 
a -1 when the model is broken (because of your change, or an earlier one 
on your branch but that 2nd case isn't frequent), then you can amend your 
patch and submit it again until you get a +1 and permission to merge via 
Gerrit if everything seems good. This workflow prevents from breaking 
"production" branches.
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Partially signed OCL M4 contribution

[Ed Willink]

Hi

Two days later, the signer seems ok again.

OCL M4a contribution contributed.

Regards

Ed Willink

On 15/12/2015 11:03, Ed Willink wrote:

Hi

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

The OCL M4 contribution is only partially signed. I tried another 
build and it is differently partially signed. Is anyone else seeing 
similar problems? Has anyone got a solution?


Regards

Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or 
unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Is projects.eclipse.org hoarked?

[Wayne Beaton]

The web team has fixed the problem.

You should be good-to-go.

Wayne

On 16/12/15 05:32 PM, Bob Brodt wrote:
Well, apparently the web team already knows about it and, according to 
Wayne, they're hard at work fixing it ;)


On Wed, Dec 16, 2015 at 3:13 PM, Matthias Sohn 
mailto:matthias.s...@gmail.com>> wrote:




On Wed, Dec 16, 2015 at 10:02 PM, Bob Brodt mailto:bbr...@redhat.com>> wrote:

Hi all,

I'm trying to create a new release record using the Project
Management Infrastructure. After entering the release number
and clicking "Create and Edit", I get a page that looks like this:



--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
EclipseCon NA 2016 
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] The Neon Opt-in Deadline is Friday

[Wayne Beaton]

The opt-in deadline for Neon is on Friday.

AFAICT, we haven't heard from these projects:

 * WindowBuilder
 * Business Process Model and Notation (BPMN2)
 * BPEL Designer
 * Target Management


If you don't opt-in, you're not in.

I've copied each of these projects' dev lists on this note (note that I 
have superpowers that allow me to post on a project mailing list without 
joining it, so I won't see your response unless you post to 
cross-project-issues-dev). If you're receiving this and your project 
doesn't have at least one representative on the cross-project-issues-dev 
mailing list, please get somebody to join.


I've confirmed the IP dates with the IP team. I've updated the Neon wiki 
page. For reference:


Dec 18/2015 - Opt-in deadline
Feb 12/2016 - CQ Submission deadline (specify that the CQ is required 
for Neon)

May 26/2016 - IP Log submission deadline
June 2/2016 - Review materials due
June 9/2016 - End of Release Review Period

I've also opened an "Every Detail Matters for Neon" bug [1]. I intend to 
drive this bug a little harder than last year's as we put more emphasis 
on user experience.


Thanks,

Wayne

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=48
--
Wayne Beaton on behalf of the Eclipse Management Organization
@waynebeaton
The Eclipse Foundation
EclipseCon NA 2016 
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Oomph's M4 may be late

[Eike Stepper]

Am 17.12.2015 um 00:15 schrieb David M Williams:
Eike, care to elaborate? Are there technical reasons I am not aware of? Or is it that you just don't want to bother, 
if the infrastructure is not working?
So our build started to fail exactly on our M4 day because of this Mac signing problem in the infrastructure. When Denis 
announced that the problem won't be fixed before Monday I tried to disable signing our Mac product, but then it seemed 
that our HIPP hit permission problems during the promotion to our downloads folder. I sent Denis a respective Skype 
question but got no reply anymore; I assume he must have been busy with other problems. I couldn't see you online 
either, so short before midnight I gave up, sent my previous note to this list and went to bed.


FWIW, today our promotion still fails with this same error:

mkdir: cannot create directory 
`/home/data/httpd/download.eclipse.org/oomph/products.tmp': Permission denied

The parent directory "oomph" does exist and seems to have correct permissions set. The last segment "products.tmp" does 
not exist, but also can't be created. I can only assume that our HIPP no longer has write permission to our main 
downloads folder (it can write to existing nested folders, though).




I assume your M3 version (which is what is currently "in the repo") will still 
"work" with the rest of the stack at M4?
Unfortunately we already missed our M3, because I was stressed by customers that day and literally forgot about it until 
it was too late. So I was really hoping to be able to contribute our M4 yesterday, mostly because we have many bug fixes 
and improvements for our community (which is quite big since we're in all packages). I don't think that our M2 build is 
problematic for the train or the packages, but I can't be 100% sure before doing some manual tests.


Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper




Thanks,




From: Eike Stepper 
To: cross-project-issues-dev@eclipse.org,
Date: 12/16/2015 05:30 PM
Subject: Re: [cross-project-issues-dev] Oomph's M4 may be late
Sent by: cross-project-issues-dev-boun...@eclipse.org




Am 16.12.2015 um 20:01 schrieb Eike Stepper:
> Hi,
>
> I just wanted to let you know that Oomph's M4 may be late today because of
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=484438
Sorry, Oomph won't contribute an M4.

Cheers
/Eike


http://www.esc-net.de 
http://thegordian.blogspot.com 
http://twitter.com/eikestepper


>
> Cheers
> /Eike
>
> 
> http://www.esc-net.de 
> http://thegordian.blogspot.com 
> http://twitter.com/eikestepper
>
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev





___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] "Aggregation model is inconsistent"errors

[Eike Stepper]

Am 17.12.2015 um 00:31 schrieb David M Williams:

Ah, I'm glad this message finally came through ... it all depends on the "luck of 
the queue" or something.

BUT, I have reinstalled, and even re-cloned, and still seeing the same problem with 'categories' in the b3 editor. 
Does anyone else? If I select the "validate" action it shows me there are several features in the Modeling Category 
that are "un-referenced" (or something like that). There is about 8 total. I'm not sure if features were attempted to 
be removed from the Modeling category? Or if some were being added?


In any case, Modeling projects should be sure to take a look at "staging" repo, to make sure all is as intended. I 
think "everything is in" the repository, and this is just a category issue, since if I pick "validate aggregation" it 
passes OK.
It seems that all the problems have been introduced by different commits of Anthony Hunter (cc'ed in a separate mail) 1 
or 2 days ago. Validate detects the following errors, for which I've added the respective commits:




commit 4ded350dbeea781ffc6a87c18c9c0d3294b25c1e (one feature removed)
Committer: Anthony Hunter  2015-12-16 01:59:09


 (DUP)

 (DUP)


commit 7dc9d997c30c1b86e59f202380626f40db765556 (two features removed)
Committer: Anthony Hunter  2015-12-15 23:15:16





commit 94758639874aa4e29a5577d70f77bb44cf7356a5 (two features removed)
Committer: Anthony Hunter  2015-12-15 20:16:48





commit c1d3ff108bf56f49214efdad95c5a0c50049d62c (two features removed)
Committer: Anthony Hunter  2015-12-15 20:16:23

I hope that helps to fix it.

Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper





I have opened bug 484518[1] to track the difference in "results" between 
various forms of 'validate'.

Thanks

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





From: David M Williams/Raleigh/IBM@IBMUS
To: Cross project issues ,
Date: 12/16/2015 05:52 PM
Subject: Re: [cross-project-issues-dev] "Aggregation model is inconsistent" 
   errors
Sent by: cross-project-issues-dev-boun...@eclipse.org




Michael, Yes, I agree that "if you are going to fail a build, a Gerrit build it the best kind to fail" ... but, still, 
I wouldn't exactly call it a "good thing" when someone makes an all too common of an error.

But, I indeed would not have to "revert" anything in that case, and that *is* a 
good thing. :)

As for the "categories". I was basing my statement on my "local run" in the b3 aggegator editor and I think I must 
have something wrong with my install, so I will try to fix that up today to avoid future false alarms.


Thanks,



From: Mickael Istria 
To: cross-project-issues-dev@eclipse.org,
Date: 12/16/2015 04:02 AM
Subject: Re: [cross-project-issues-dev] "Aggregation model is inconsistent" 
errors
Sent by: cross-project-issues-dev-boun...@eclipse.org




On 12/16/2015 09:39 AM, David M Williams wrote:
As of right now, the 'head' of the model is breaking due to invalid "categories" and the "Gerrit job" is breaking due 
to invalid "contacts".

@David:
As far as I can see, the failing Gerrit job is a good thing, since it did vote -1 on an ongoing review, and it helped 
the other to fix their contribution before they could merge it.
Where is the CI job highlighting that HEAD is breaking? I'm on 
_https://hudson.eclipse.org/simrel/job/simrel.neon.runaggregator.BUILD__CLEAN/_and everything is green.


@All:
Like many are already doing, even if you're a SimRel committer and if you're using the simrel model editor, it's 
always a good idea to take advantage of the validation step offered by Gerrit: 
_https://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build#Contribute_via_a_Gerrit_review_. When 
pushing to Gerrit, the model is automatically validated and you get a -1 when the model is broken (because of your 
change, or an earlier one on your branch but that 2nd case isn't frequent), then you can amend your patch and submit 
it again until you get a +1 and permission to merge via Gerrit if everything seems good. This workflow prevents from 
breaking "production" branches.

--
Mickael Istria
Eclipse developer at _JBoss, by Red Hat_ _
__My blog_ - _My Tweets_ 
___

cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit_
__https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev_
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.o

[cross-project-issues-dev] Declaring Neon M4 repository done

[David M Williams]

It is not quite, literally "done", since the last "CLEAN" job is still 
running, with Eike's attempt to fix-up the modeling features. 
While that may take a few hours to finish, I have a appointment "first 
thing" in the morning, so must go to bed early. 

But, I have disabled "validate jobs" which is where the work flow starts. 

FYI, I am not completely opposed to "re-building", on Thursday,  if some 
of the technical infrastructure problems are fixed early Thursday ... 
But I did not want to wait until Monday when some *might* be fixed, since 
as I understand it, some people will be on holiday by then -- when it 
rains, it pours. 

So, we'll do the best we can with what we have, and THEN decide if we need 
to postpone the whole thing, do to these various issues. I think (by 
intuition) we will be fine, for an M4 deliverable, and then can 
hit the ground running for M5? 

Also, to give you warning, I have not looked closely at the input, to see 
if everyone who has "declared by M4" is actually *in* M4. Sorry I've not 
had time to police that and so far do not have an automated way to tell. 

Thanks for everyone's help and patience. 





From:   Eike Stepper 
To: cross-project-issues-dev@eclipse.org, 
Date:   12/17/2015 12:49 AM
Subject:Re: [cross-project-issues-dev] "Aggregation model is 
inconsistent"errors
Sent by:cross-project-issues-dev-boun...@eclipse.org



Am 17.12.2015 um 00:31 schrieb David M Williams:
> Ah, I'm glad this message finally came through ... it all depends on the 
"luck of the queue" or something.
>
> BUT, I have reinstalled, and even re-cloned, and still seeing the same 
problem with 'categories' in the b3 editor. 
> Does anyone else? If I select the "validate" action it shows me there 
are several features in the Modeling Category 
> that are "un-referenced" (or something like that). There is about 8 
total. I'm not sure if features were attempted to 
> be removed from the Modeling category? Or if some were being added?
>
> In any case, Modeling projects should be sure to take a look at 
"staging" repo, to make sure all is as intended. I 
> think "everything is in" the repository, and this is just a category 
issue, since if I pick "validate aggregation" it 
> passes OK.
It seems that all the problems have been introduced by different commits 
of Anthony Hunter (cc'ed in a separate mail) 1 
or 2 days ago. Validate detects the following errors, for which I've added 
the respective commits:



 commit 4ded350dbeea781ffc6a87c18c9c0d3294b25c1e (one feature removed)
 Committer: Anthony Hunter  2015-12-16 01:59:09


 
(DUP)

 
(DUP)


 commit 7dc9d997c30c1b86e59f202380626f40db765556 (two features 
removed)
 Committer: Anthony Hunter  2015-12-15 23:15:16





 commit 94758639874aa4e29a5577d70f77bb44cf7356a5 (two features 
removed)
 Committer: Anthony Hunter  2015-12-15 20:16:48





 commit c1d3ff108bf56f49214efdad95c5a0c50049d62c (two features 
removed)
 Committer: Anthony Hunter  2015-12-15 20:16:23

I hope that helps to fix it.

Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper



>
> I have opened bug 484518[1] to track the difference in "results" between 
various forms of 'validate'.
>
> Thanks
>
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=484518
>
>
>
>
>
> From: David M Williams/Raleigh/IBM@IBMUS
> To: Cross project issues ,
> Date: 12/16/2015 05:52 PM
> Subject: Re: [cross-project-issues-dev] "Aggregation model is 
inconsistent"errors
> Sent by: cross-project-issues-dev-boun...@eclipse.org
> 

>
>
>
> Michael, Yes, I agree that "if you are going to fail a build, a Gerrit 
build it the best kind to fail" ... but, still, 
> I wouldn't exactly call it a "good thing" when someone makes an all too 
common of an error.
> But, I indeed would not have to "revert" anything in that case, and that 
*is* a good thing. :)
>
> As for the "categories". I was basing my statement on my "local run" in 
the b3 aggegator editor and I think I must 
> have something wrong with my install, so I will try to fix that up today 
to avoid future false alarms.
>
> Thanks,
>
>
>
> From: Mickael Istria 
> To: cross-project-issues-dev@eclipse.org,
> Date: 12/16/2015 04:02 AM
> Subject: Re: [cross-project-issues-dev] "Aggregation model is 
inconsistent" errors
> Sent by: cross-project-issues-dev-boun...@eclipse.org
> 

>
>
>
> On 12/16/2015 09:39 AM, David M Williams wrote:
> As of right now, the 'head' of the model is breaking due to invalid 
"categories" and the "Gerrit job" is breaking due 
> to invalid "contacts".
> @David:
> As far as I can see, the failing Gerrit job is a good thing, since it 
did vote -1 on an ongoing review, and it helped 
> the oth

Re: [cross-project-issues-dev] Oomph's M4 may be late (UPDATE!)

[Eike Stepper]

Hi David,

I noticed that the last Neon CLEAN aggregation yesterday failed. In the hope that we have a last chance to contribute 
our M4 today I could change our build to work around the permission problems (that probably resulted from a HIPP restart 
I requested yesterday). I've manually promoted the relevant artifacts and updated our .b3aggrcon file accordingly. 
Please let me know if it'll make it in.


Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper





Am 17.12.2015 um 06:18 schrieb Eike Stepper:

Am 17.12.2015 um 00:15 schrieb David M Williams:
Eike, care to elaborate? Are there technical reasons I am not aware of? Or is it that you just don't want to bother, 
if the infrastructure is not working?
So our build started to fail exactly on our M4 day because of this Mac signing problem in the infrastructure. When 
Denis announced that the problem won't be fixed before Monday I tried to disable signing our Mac product, but then it 
seemed that our HIPP hit permission problems during the promotion to our downloads folder. I sent Denis a respective 
Skype question but got no reply anymore; I assume he must have been busy with other problems. I couldn't see you 
online either, so short before midnight I gave up, sent my previous note to this list and went to bed.


FWIW, today our promotion still fails with this same error:

mkdir: cannot create directory 
`/home/data/httpd/download.eclipse.org/oomph/products.tmp': Permission denied

The parent directory "oomph" does exist and seems to have correct permissions set. The last segment "products.tmp" 
does not exist, but also can't be created. I can only assume that our HIPP no longer has write permission to our main 
downloads folder (it can write to existing nested folders, though).




I assume your M3 version (which is what is currently "in the repo") will still 
"work" with the rest of the stack at M4?
Unfortunately we already missed our M3, because I was stressed by customers that day and literally forgot about it 
until it was too late. So I was really hoping to be able to contribute our M4 yesterday, mostly because we have many 
bug fixes and improvements for our community (which is quite big since we're in all packages). I don't think that our 
M2 build is problematic for the train or the packages, but I can't be 100% sure before doing some manual tests.


Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper




Thanks,




From: Eike Stepper 
To: cross-project-issues-dev@eclipse.org,
Date: 12/16/2015 05:30 PM
Subject: Re: [cross-project-issues-dev] Oomph's M4 may be late
Sent by: cross-project-issues-dev-boun...@eclipse.org




Am 16.12.2015 um 20:01 schrieb Eike Stepper:
> Hi,
>
> I just wanted to let you know that Oomph's M4 may be late today because of
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=484438
Sorry, Oomph won't contribute an M4.

Cheers
/Eike


http://www.esc-net.de 
http://thegordian.blogspot.com 
http://twitter.com/eikestepper


>
> Cheers
> /Eike
>
> 
> http://www.esc-net.de 
> http://thegordian.blogspot.com 
> http://twitter.com/eikestepper
>
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev





___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev




___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Declaring Neon M4 repository done

[Eike Stepper]

Am 17.12.2015 um 08:41 schrieb David M Williams:
It is not quite, literally "done", since the last "CLEAN" job is still running, with Eike's attempt to fix-up the 
modeling features.

While that may take a few hours to finish, I have a appointment "first thing" 
in the morning, so must go to bed early.

I have the feeling you kicked this new build a minute before I updated my 
contribution. Can you restart it to pick it up?

Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper




But, I have disabled "validate jobs" which is where the work flow starts.

FYI, I am not completely opposed to "re-building", on Thursday,  if some of the technical infrastructure problems are 
fixed early Thursday ...
But I did not want to wait until Monday when some *might* be fixed, since as I understand it, some people will be on 
holiday by then -- when it rains, it pours.


So, we'll do the best we can with what we have, and THEN decide if we need to postpone the whole thing, do to these 
various issues. I think (by intuition) we will be fine, for an M4 deliverable, and then can

hit the ground running for M5?

Also, to give you warning, I have not looked closely at the input, to see if everyone who has "declared by M4" is 
actually *in* M4. Sorry I've not had time to police that and so far do not have an automated way to tell.


Thanks for everyone's help and patience.





From: Eike Stepper 
To: cross-project-issues-dev@eclipse.org,
Date: 12/17/2015 12:49 AM
Subject: Re: [cross-project-issues-dev] "Aggregation model is
inconsistent"errors
Sent by: cross-project-issues-dev-boun...@eclipse.org




Am 17.12.2015 um 00:31 schrieb David M Williams:
> Ah, I'm glad this message finally came through ... it all depends on the "luck of 
the queue" or something.
>
> BUT, I have reinstalled, and even re-cloned, and still seeing the same 
problem with 'categories' in the b3 editor.
> Does anyone else? If I select the "validate" action it shows me there are 
several features in the Modeling Category
> that are "un-referenced" (or something like that). There is about 8 total. 
I'm not sure if features were attempted to
> be removed from the Modeling category? Or if some were being added?
>
> In any case, Modeling projects should be sure to take a look at "staging" 
repo, to make sure all is as intended. I
> think "everything is in" the repository, and this is just a category issue, since if I 
pick "validate aggregation" it
> passes OK.
It seems that all the problems have been introduced by different commits of 
Anthony Hunter (cc'ed in a separate mail) 1
or 2 days ago. Validate detects the following errors, for which I've added the 
respective commits:



commit 4ded350dbeea781ffc6a87c18c9c0d3294b25c1e (one feature removed)
Committer: Anthony Hunter  2015-12-16 01:59:09


 (DUP)

 (DUP)


commit 7dc9d997c30c1b86e59f202380626f40db765556 (two features removed)
Committer: Anthony Hunter  2015-12-15 23:15:16





commit 94758639874aa4e29a5577d70f77bb44cf7356a5 (two features removed)
Committer: Anthony Hunter  2015-12-15 20:16:48





commit c1d3ff108bf56f49214efdad95c5a0c50049d62c (two features removed)
Committer: Anthony Hunter  2015-12-15 20:16:23

I hope that helps to fix it.

Cheers
/Eike


http://www.esc-net.de 
http://thegordian.blogspot.com 
http://twitter.com/eikestepper



>
> I have opened bug 484518[1] to track the difference in "results" between 
various forms of 'validate'.
>
> Thanks
>
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=484518
>
>
>
>
>
> From: David M Williams/Raleigh/IBM@IBMUS
> To: Cross project issues ,
> Date: 12/16/2015 05:52 PM
> Subject: Re: [cross-project-issues-dev] "Aggregation model is inconsistent"   
 errors
> Sent by: cross-project-issues-dev-boun...@eclipse.org
> 

>
>
>
> Michael, Yes, I agree that "if you are going to fail a build, a Gerrit build it 
the best kind to fail" ... but, still,
> I wouldn't exactly call it a "good thing" when someone makes an all too 
common of an error.
> But, I indeed would not have to "revert" anything in that case, and that *is* 
a good thing. :)
>
> As for the "categories". I was basing my statement on my "local run" in the 
b3 aggegator editor and I think I must
> have something wrong with my install, so I will try to fix that up today to 
avoid future false alarms.
>
> Thanks,
>
>
>
> From: Mickael Istria 
> To: cross-project-issues-dev@eclipse.org,
> Date: 12/16/2015 04:02 AM
> Subject: Re: [cross-project-issues-dev] "Aggregation model is inconsistent" 
errors
> Sent by: cross-project-issues-dev-boun...@eclipse.org
> 
-