More details of which test package consumed how much time:

30322 
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/405/label=linux-stable-worker/testReport/?
30323 
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/406/label=linux-stable-worker/testReport/?

could it be, that the superclass method check causes so much more overhead?
I definitely see 250 newly executed tests, but that accounts for ~2% of the 
tests...

On 2013-08-21, at 14:36, Camillo Bruni <[email protected]> wrote:

> The current build times for pharo are 3mins slower than when I left on 
> holidays, what happened?
> 
> https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/buildTimeTrend
> 
> => between august 5 and 6, we got 2.5 minutes slower under the mac slave!
> 
> I assume it's update 30323
> https://github.com/pharo-project/pharo-core/commit/acf125b589ee03bef1d028ddda00afbc98f645d8


Reply via email to