Re: [Pharo-dev] FogBugz (Case [Issue]16520) CI and Bugtracker - Help topic for how to contribute to Pharo basecode
Hi! Apparently the fix needs more work. But I am not sure how to proceed. The monkey says: a CIAndRule: Timeout (after 0:01:00:00) occured while loading "Help topic for how to contribute to Pharo basecode" What can I do? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Sep 9, 2015, at 4:45 AM, Pharo Issue Tracker <do-not-reply@pharo.fogbugz.com> wrote:
Ulysse The Galactic Monkey From Outer Spaceedited Case 16520: Help topic for how to contribute to Pharo basecode <https://pharo.fogbugz.com/f/cases/16520>:
Bug in CI and Bugtracker: 1. Pharo Image
Issue Validation Failed: https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/13183//artifact/vali... <https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/13183//artifact/vali...> Errors: 1 |
Status changed: Resolved (Monkey is checking) Work Needed
Priority: 5 â Fix If Time Status: Work Needed Assigned to: Alexandre Bergel Milestone: Pharo5.0
Go to Case
<https://pharo.fogbugz.com/f/cases/16520> Don't want FogBugz notifications anymore? Update your preferences. <https://pharo.fogbugz.com/f/userPrefs>
Not much mark it as fix to include. 4 Le 9/9/15 19:07, Alexandre Bergel a écrit :
Hi!
Apparently the fix needs more work. But I am not sure how to proceed. The monkey says:
*
a CIAndRule: Timeout (after 0:01:00:00) occured while loading "Help topic for how to contribute to Pharo basecode"
What can I do?
Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Sep 9, 2015, at 4:45 AM, Pharo Issue Tracker <do-not-reply@pharo.fogbugz.com <mailto:do-not-reply@pharo.fogbugz.com>> wrote:
avatar *Ulysse The Galactic Monkey From Outer Space*edited*Case 16520*: Help topic for how to contribute to Pharo basecode <https://pharo.fogbugz.com/f/cases/16520>: *Bug*inProject: CI and Bugtracker: 1. Pharo Image
Issue Validation Failed:https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/13183//artifact/vali... Errors: 1 |
*Status*changed: Resolved (Monkey is checking)changed to Work Needed
Priority *Priority*: 5 â Fix If Time Status *Status*: Work Needed Assigned To *Assigned to*: Alexandre Bergel Milestone *Milestone*: Pharo5.0
Go to Case <https://pharo.fogbugz.com/f/cases/16520> Don't want FogBugz notifications anymore?Update your preferences. <https://pharo.fogbugz.com/f/userPrefs>
FogBugz
On 09 Sep 2015, at 20:27, stepharo <stepharo@free.fr> wrote:
Not much mark it as fix to include.
The last where this was done added an undeclared. Quality goes down very fast when we add changes without running the tests. Marcus
yes in that case why not fixing that because this is really really annoying to always get a fix rejected with a bad feedback. Stef Le 9/9/15 21:52, Marcus Denker a écrit :
On 09 Sep 2015, at 20:27, stepharo <stepharo@free.fr> wrote:
Not much mark it as fix to include. The last where this was done added an undeclared. Quality goes down very fast when we add changes without running the tests.
Marcus
Maybe change the error message until it is resolved to something like "Timeout blablabla... this is CI issue, please tell the monkey to try again". So people know it's not their error and it will also tell them what to do, so they (me last week, Alex this week, someone else next week) don't need to ask again and again. Peter On Wed, Sep 9, 2015 at 9:57 PM, stepharo <stepharo@free.fr> wrote:
yes in that case why not fixing that because this is really really annoying to always get a fix rejected with a bad feedback.
Stef
Le 9/9/15 21:52, Marcus Denker a écrit :
On 09 Sep 2015, at 20:27, stepharo <stepharo@free.fr> wrote:
Not much mark it as fix to include.
The last where this was done added an undeclared. Quality goes down very fast when we add changes without running the tests.
Marcus
It needs to be fixed but I *really* did not find any time yet.
On 09 Sep 2015, at 22:00, Peter Uhnák <i.uhnak@gmail.com> wrote:
Maybe change the error message until it is resolved to something like "Timeout blablabla... this is CI issue, please tell the monkey to try again". So people know it's not their error and it will also tell them what to do, so they (me last week, Alex this week, someone else next week) don't need to ask again and again.
Peter
On Wed, Sep 9, 2015 at 9:57 PM, stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> wrote: yes in that case why not fixing that because this is really really annoying to always get a fix rejected with a bad feedback.
Stef
Le 9/9/15 21:52, Marcus Denker a écrit :
On 09 Sep 2015, at 20:27, stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> wrote:
Not much mark it as fix to include. The last where this was done added an undeclared. Quality goes down very fast when we add changes without running the tests.
Marcus
I did some workaround for now => disabled some not that useful checks => put the timout higher a normal run is now at around 30 min.
On 09 Sep 2015, at 22:05, Marcus Denker <marcus.denker@inria.fr> wrote:
It needs to be fixed but I *really* did not find any time yet.
On 09 Sep 2015, at 22:00, Peter Uhnák <i.uhnak@gmail.com <mailto:i.uhnak@gmail.com>> wrote:
Maybe change the error message until it is resolved to something like "Timeout blablabla... this is CI issue, please tell the monkey to try again". So people know it's not their error and it will also tell them what to do, so they (me last week, Alex this week, someone else next week) don't need to ask again and again.
Peter
On Wed, Sep 9, 2015 at 9:57 PM, stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> wrote: yes in that case why not fixing that because this is really really annoying to always get a fix rejected with a bad feedback.
Stef
Le 9/9/15 21:52, Marcus Denker a écrit :
On 09 Sep 2015, at 20:27, stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> wrote:
Not much mark it as fix to include. The last where this was done added an undeclared. Quality goes down very fast when we add changes without running the tests.
Marcus
Thanks Marcus! Apparently my two fixes are now in. This is cool! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Sep 10, 2015, at 11:23 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
I did some workaround for now
=> disabled some not that useful checks => put the timout higher
a normal run is now at around 30 min.
On 09 Sep 2015, at 22:05, Marcus Denker <marcus.denker@inria.fr <mailto:marcus.denker@inria.fr>> wrote:
It needs to be fixed but I *really* did not find any time yet.
On 09 Sep 2015, at 22:00, Peter Uhnák <i.uhnak@gmail.com <mailto:i.uhnak@gmail.com>> wrote:
Maybe change the error message until it is resolved to something like "Timeout blablabla... this is CI issue, please tell the monkey to try again". So people know it's not their error and it will also tell them what to do, so they (me last week, Alex this week, someone else next week) don't need to ask again and again.
Peter
On Wed, Sep 9, 2015 at 9:57 PM, stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> wrote: yes in that case why not fixing that because this is really really annoying to always get a fix rejected with a bad feedback.
Stef
Le 9/9/15 21:52, Marcus Denker a écrit :
On 09 Sep 2015, at 20:27, stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> wrote:
Not much mark it as fix to include. The last where this was done added an undeclared. Quality goes down very fast when we add changes without running the tests.
Marcus
+ 1 This is important! Stef Le 10/9/15 16:30, Alexandre Bergel a écrit :
Thanks Marcus! Apparently my two fixes are now in. This is cool!
Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Sep 10, 2015, at 11:23 AM, Marcus Denker <marcus.denker@inria.fr <mailto:marcus.denker@inria.fr>> wrote:
I did some workaround for now
=> disabled some not that useful checks => put the timout higher
a normal run is now at around 30 min.
On 09 Sep 2015, at 22:05, Marcus Denker <marcus.denker@inria.fr <mailto:marcus.denker@inria.fr>> wrote:
It needs to be fixed but I *really* did not find any time yet.
On 09 Sep 2015, at 22:00, Peter Uhnák <i.uhnak@gmail.com <mailto:i.uhnak@gmail.com>> wrote:
Maybe change the error message until it is resolved to something like "Timeout blablabla... this is CI issue, please tell the monkey to try again". So people know it's not their error and it will also tell them what to do, so they (me last week, Alex this week, someone else next week) don't need to ask again and again.
Peter
On Wed, Sep 9, 2015 at 9:57 PM, stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> wrote:
yes in that case why not fixing that because this is really really annoying to always get a fix rejected with a bad feedback.
Stef
Le 9/9/15 21:52, Marcus Denker a écrit :
On 09 Sep 2015, at 20:27, stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> wrote:
Not much mark it as fix to include.
The last where this was done added an undeclared. Quality goes down very fast when we add changes without running the tests.
Marcus
This is happening since last week (or maybe even earlier), you can also keep telling the monkey to try again until it succeeds. On Wed, Sep 9, 2015 at 8:27 PM, stepharo <stepharo@free.fr> wrote:
Not much mark it as fix to include. 4
Le 9/9/15 19:07, Alexandre Bergel a écrit :
Hi!
Apparently the fix needs more work. But I am not sure how to proceed. The monkey says:
- a CIAndRule: Timeout (after 0:01:00:00) occured while loading "Help topic for how to contribute to Pharo basecode"
What can I do?
Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Sep 9, 2015, at 4:45 AM, Pharo Issue Tracker < do-not-reply@pharo.fogbugz.com> wrote:
[image: avatar] *Ulysse The Galactic Monkey From Outer Space*edited *Case 16520*: Help topic for how to contribute to Pharo basecode <https://pharo.fogbugz.com/f/cases/16520>: *Bug* in [image: Project:] CI and Bugtracker: 1. Pharo Image Issue Validation Failed: <https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/13183//artifact/vali...> https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/13183//artifact/vali... Errors: 1 | *Status* changed: Resolved (Monkey is checking) [image: changed to] Work Needed
[image: Priority] *Priority*: 5 â Fix If Time [image: Status] *Status*: Work Needed [image: Assigned To] *Assigned to*: Alexandre Bergel [image: Milestone] *Milestone*: Pharo5.0
Go to Case <https://pharo.fogbugz.com/f/cases/16520> Don't want FogBugz notifications anymore? Update your preferences. <https://pharo.fogbugz.com/f/userPrefs>
[image: FogBugz]
Yes, I need to block some time to look why this happens.
On 09 Sep 2015, at 21:53, Peter Uhnák <i.uhnak@gmail.com> wrote:
This is happening since last week (or maybe even earlier), you can also keep telling the monkey to try again until it succeeds.
On Wed, Sep 9, 2015 at 8:27 PM, stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> wrote: Not much mark it as fix to include. 4
Le 9/9/15 19:07, Alexandre Bergel a écrit :
Hi!
Apparently the fix needs more work. But I am not sure how to proceed. The monkey says: a CIAndRule: Timeout (after 0:01:00:00) occured while loading "Help topic for how to contribute to Pharo basecode" What can I do?
Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Sep 9, 2015, at 4:45 AM, Pharo Issue Tracker <do-not-reply@pharo.fogbugz.com <mailto:do-not-reply@pharo.fogbugz.com>> wrote:
Ulysse The Galactic Monkey From Outer Spaceedited Case 16520: Help topic for how to contribute to Pharo basecode <https://pharo.fogbugz.com/f/cases/16520>:
Bug in CI and Bugtracker: 1. Pharo Image
Issue Validation Failed: <https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/13183//artifact/validationReport.html>https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/13183//artifact/validationReport.html <https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/13183//artifact/vali...> Errors: 1 | Status changed: Resolved (Monkey is checking) Work Needed
Priority: 5 â Fix If Time Status: Work Needed Assigned to: Alexandre Bergel Milestone: Pharo5.0
Go to Case
<https://pharo.fogbugz.com/f/cases/16520> Don't want FogBugz notifications anymore? Update your preferences. <https://pharo.fogbugz.com/f/userPrefs>
participants (4)
-
Alexandre Bergel -
Marcus Denker -
Peter Uhnák -
stepharo