Re: [papyrus-rt-dev] Missing Papyrus perspective and new project/mode wi

[Christian Damus <give.a.damus@xxxxxxxxx>]

Hi, Peter,

I just ran a the tester Oomph setup and got Papyrus 2.0.4.201703160146.  Papyrus perspective looks OK and I can create and edit a UML-RT for C++ model.

Any clues in your error log?

Cheers,

Christian

On Mar 16, 2017, 08:53 -0400, Peter Cigéhn <peter.cigehn@xxxxxxxxx>, wrote:

Hi,

Is it someone else that have problems with the nightly build of Papyrus-RT, based on the tester setup where you are using the nightly builds of Papyrus?

I asked on the Papyrus developer list and Papyrus developers claim that they can't see this issue with the latest Papyrus Neon build.

Is it my p2 bundle pool that has gone "bananas", which I am a bit reluctant on "nuking".

Can someone confirm if they have the same issue with the their tester setup? Or am I the only one? :(

/Peter Cigéhn

On 16 March 2017 at 12:33, Peter Cigéhn <peter.cigehn@xxxxxxxxx> wrote:

Hi,

Yes, that seem to have re-triggered all needed builds. 

Unfortunately we seem to have gotten a major regression in the nightly build of Papyrus Neon, which seem to be very similar to the issue I bumped into yesterday for the nightly build of Papyrus Oxygen. The Papyrus perspective is gone, and no Papyrus project/model wizard is available... :(

The issue for Papyrus Oxygen was solved, and today the nightly build of Papyrus Oxygen has the perspective and new model/project wizard is back. But then the regression has occurred for Neon instead... What is going here? Quentin's response on the Papyrus developer mailing list does not indicate what the fix that was made was about.

/Peter Cigéhn

On 16 March 2017 at 10:57, Remi Schnekenburger <rschnekenburger@eclipsesource.com> wrote:

Hi Peter,

I triggered a new build for Core (#415).

I also modified configuration for tooling and core build jobs, so you can also trigger them. Please tell me if you still cannot trigger the build.

Cheers,

Rémi

2017-03-16 9:33 GMT+01:00 Peter Cigéhn <peter.cigehn@xxxxxxxxx>:

Hi,

Currently we have a failed core build (#414) and after that we have a successful product build (#514). I am not sure if I can trust the product build though, when the core build have failed (which should have triggered a build of tooling also).

I only have access right to re-trigger product builds. Could someone re-trigger the failing core build? It seem to have failed due to a null pointer exception in one of the core tests, which just looks strange.

I would like to test Christian fixes to bug 513066, but would like to be really sure that they actually are included in the build (I had some issues yesterday when testing one of Ernesto's fixes that for some reason had made it into the build).

/Peter Cigéhn

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev

--

Remi Schnekenburger

Senior Software Architect / General Manager

EclipseSource Paris

Email: rschnekenburger@eclipsesource.com
Web: http://eclipsesource.com/paris 
Phone: +33 1 85 41 08 65

German Phone: +49 89 21 555 30 - 25

Fax: +49 89 21 555 30 - 19

Hangouts: rschnekenburger@eclipsesource.com

EclipseSource France SAS
7 rue de la Croix Martre
91120 Palaiseau

General Manager: Remi Schnekenburger

Registered Office: 7 rue de la Croix Martre, 91120 Palaiseau, France

Commercial Register 824 977 516  R.C.S. EVRY

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev