CI does not finish (PR 309)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

CI does not finish (PR 309)

Torsten Bergmann
For whatever reason the CI jobs for PR's to Pharo 7 runs endless and never finishes.
It run well a few days ago ...

https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/PR-309/

Any ideas?


Reply | Threaded
Open this post in threaded view
|

Re: CI does not finish (PR 309)

Marcus Denker-4
I think the reason is that the last image opens an epicea window
to recover code… which it should not.

> On 29 Sep 2017, at 10:38, Torsten Bergmann <[hidden email]> wrote:
>
> For whatever reason the CI jobs for PR's to Pharo 7 runs endless and never finishes.
> It run well a few days ago ...
>
> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/PR-309/
>
> Any ideas?
>
>


Reply | Threaded
Open this post in threaded view
|

Re: CI does not finish (PR 309)

Marcus Denker-4
No, it seems to work.. we now had some issues where the test run was successful

        Marcus

> On 29 Sep 2017, at 10:52, Marcus Denker <[hidden email]> wrote:
>
> I think the reason is that the last image opens an epicea window
> to recover code… which it should not.
>
>> On 29 Sep 2017, at 10:38, Torsten Bergmann <[hidden email]> wrote:
>>
>> For whatever reason the CI jobs for PR's to Pharo 7 runs endless and never finishes.
>> It run well a few days ago ...
>>
>> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/PR-309/
>>
>> Any ideas?
>>
>>
>


Reply | Threaded
Open this post in threaded view
|

Re: CI does not finish (PR 309)

Torsten Bergmann
I'm lost on this one and would really appreciate if someone could check
why it is blocked in the CI (it was running green a few days ago and
I only changed SmalltalkImage>>#lastUpdateString. All other changes where
just to retrigger the CI.

The log does not tell me anything useful beside that it is always
hanging at the same point

   2017-09-29 12:33:04 (573 KB/s) - ‘idea11.zip’ saved [152003/152003]
   [Compiler] Installing RPackage

Thanks
T.

> Gesendet: Freitag, 29. September 2017 um 12:56 Uhr
> Von: "Marcus Denker" <[hidden email]>
> An: "Pharo Development List" <[hidden email]>
> Betreff: Re: [Pharo-dev] CI does not finish (PR 309)
>
> No, it seems to work.. we now had some issues where the test run was successful
>
> Marcus
>
> > On 29 Sep 2017, at 10:52, Marcus Denker <[hidden email]> wrote:
> >
> > I think the reason is that the last image opens an epicea window
> > to recover code… which it should not.
> >
> >> On 29 Sep 2017, at 10:38, Torsten Bergmann <[hidden email]> wrote:
> >>
> >> For whatever reason the CI jobs for PR's to Pharo 7 runs endless and never finishes.
> >> It run well a few days ago ...
> >>
> >> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/PR-309/
> >>
> >> Any ideas?
> >>
> >>
> >
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: CI does not finish (PR 309)

tinchodias
In reply to this post by Marcus Denker-4


On Fri, Sep 29, 2017 at 5:52 AM, Marcus Denker <[hidden email]> wrote:
I think the reason is that the last image opens an epicea window
to recover code… which it should not.

The setting to do that is disabled by default (at least I did that before 6.0 release).

BTW, ~Sunday night I fixed test errors of epicea in p7. The reason was that Class, Trait and metas do not use the TClass trait. 
It's in #development but still not in #stable. I still have to read the mailing list how to integrate a new epicea version in P7 (I guess a PR).

 
 

> On 29 Sep 2017, at 10:38, Torsten Bergmann <[hidden email]> wrote:
>
> For whatever reason the CI jobs for PR's to Pharo 7 runs endless and never finishes.
> It run well a few days ago ...
>
> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/PR-309/
>
> Any ideas?
>
>