+ 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 <[email protected]
<mailto:[email protected]>> 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 <[email protected]
<mailto:[email protected]>> 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 <[email protected]
<mailto:[email protected]>> 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 <[email protected]
<mailto:[email protected]>> 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 <[email protected]
<mailto:[email protected]>> 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
