On Wed, Sep 22, 2010 at 11:59 PM, Antoine Toulme wrote:
> Can you share with us the bug number once you filed it ?
http://issues.hudson-ci.org/browse/HUDSON-7535
/niklas
Can you share with us the bug number once you filed it ?
On Wed, Sep 22, 2010 at 00:19, Niklas Gustavsson wrote:
> On Wed, Sep 22, 2010 at 12:07 AM, Jesse Glick
> wrote:
> > On 09/21/2010 04:37 PM, Niklas Gustavsson wrote:
> >>
> >> If anyone got any idea, besides asking the Hudson devs to optim
On Wed, Sep 22, 2010 at 12:07 AM, Jesse Glick wrote:
> On 09/21/2010 04:37 PM, Niklas Gustavsson wrote:
>>
>> If anyone got any idea, besides asking the Hudson devs to optimize
>> this code
>
> Sounds like a clear bug in Hudson; will you file it?
Yes, that's my plan.
/niklas
On 09/21/2010 04:37 PM, Niklas Gustavsson wrote:
If anyone got any idea, besides asking the Hudson devs to optimize
this code
Sounds like a clear bug in Hudson; will you file it?
On Tue, Sep 21, 2010 at 10:41 PM, Ted Dunning wrote:
> Ouch. It sounds like the easiest optimization would be to not do this
> computation if the dependencies for the current job have not changed.
Right, in the current code, as far as I understand it, the dependency
graph is rebuilt twice, no ma
Ouch. It sounds like the easiest optimization would be to not do this
computation if the dependencies for the current job have not changed.
That would be easier than doing the correct thing which would be to
propagate simply changes until the system reaches something unchanged.
On Tue, Sep 21, 2
On Tue, Sep 21, 2010 at 9:44 PM, Niklas Gustavsson wrote:
> On Tue, Sep 21, 2010 at 5:52 PM, Jesse Glick wrote:
>> I had thought this was just a problem with the old Hudson installation, but
>> it is still true: clicking "Save" from a job's /configure screen takes
>> several minutes before the jo
On Tue, Sep 21, 2010 at 5:52 PM, Jesse Glick wrote:
> I had thought this was just a problem with the old Hudson installation, but
> it is still true: clicking "Save" from a job's /configure screen takes
> several minutes before the job's main page is loaded again. This should only
> take a second
I had thought this was just a problem with the old Hudson installation, but it is still true: clicking "Save" from a job's /configure screen takes several minutes before
the job's main page is loaded again. This should only take a second or two. Maybe someone can trace what is taking so long?
