Evaluation 338[1] is triggered by commit 1d8d69c[2], which only updates
the documentation. This evaluation produces 86 useless tests:
test.mcron.i686-linux, test.opensmtpd.i686-linux, etc. I believe those
tests are triggered at each evaluation (almost), and it's a considerable
waste of resources.
The 'core-updates' and 'staging' branches shouldn't trigger evaluations
at each commit, because they produce too many derivations. Instead, the
admins should have a 'trigger evaluation' button that they use once in a
while. That button should be part of an 'admin interface', which should
be prote
Clément Lassieur ezt írta (időpont: 2018. aug. 27.,
H, 11:54):
> The 'core-updates' and 'staging' branches shouldn't trigger evaluations
> at each commit, because they produce too many derivations. Instead, the
> admins should have a 'trigger evaluation' button that they use once in a
> while.
Hi,
Carlo Zancanaro skribis:
> Pushed! Thanks for the review.
Great!
I see that you also reverted the patch that removed the ‘EINTR-safe’
workaround. Could you explain why that was necessary? (It should not
be necessary with current Guile versions.)
Thank you,
Ludo’.
Gábor Boskovits writes:
> Clément Lassieur ezt írta (időpont: 2018. aug. 27.,
> H, 11:54):
>
>> The 'core-updates' and 'staging' branches shouldn't trigger evaluations
>> at each commit, because they produce too many derivations. Instead, the
>> admins should have a 'trigger evaluation' butto
On Mon, Aug 27 2018, Ludovic Courtès wrote:
I see that you also reverted the patch that removed the
‘EINTR-safe’ workaround. Could you explain why that was
necessary? (It should not be necessary with current Guile
versions.)
I'm not really sure of the details, but as I mentioned on IRC,
th
Hi Clément,
in the future I plan on making the actual bin/evaluate use another database
connection
in order for the web interface to be isolated while it's querying.
Otherwise - as it is now in master - it can happen that while you are querying
one
page, half of the things have different values
Hi Danny,
Danny Milosavljevic writes:
> Hi Clément,
>
> in the future I plan on making the actual bin/evaluate use another database
> connection
> in order for the web interface to be isolated while it's querying.
I don't understand... bin/evaluate doesn't query the database at all. I
don't k
Ludovic Courtès writes:
> Hi Clément,
>
> Clément Lassieur skribis:
>
>> Ludovic Courtès writes:
>>
>>> Excellent, thanks for working on this! This looks great to me, and I
>>> think the pros outweigh the cons. Did you check on a big database how
>>> well it performs?
>>
>> Yes, I didn't se
Hi Clément,
I've read through the patch and it seems to handle the case I mean fine because
you support an arbitrary number of queries per db critical section - so I agree
that this patchset is fine.
Keep in mind this is only fine if the critical section is held over an entire
http
request handl
Thank you for the explanation Danny.
Indeed I didn't fix what you described. That could be done easily by
wrapping the handler with WITH-DB-CRITICAL-SECTION. I'm not sure about
the consequences in terms of performance, given that this will send a
huge function to a channel, and that all the work
Carlo Zancanaro writes:
>>Anyway, it all LGTM, thanks!
>
> Pushed! Thanks for the review.
>
> Carlo
Awesome! Thanks a lot Carlo for working on this :-)
As discussed earlier today on IRC with Clément, we could add performance
monitoring capabilities to Cuirass. Interesting metrics would be:
• time of push to time of evaluation completion;
• time of evaluation completion to time of build completion.
We could visualize that per job over time.
On 2018-05-04, Vagrant Cascadian wrote:
> Many of the icons appear to be missing from the user interface, such as
> the button for "Power on", "Pause the virtual machine", "Shut down the
> virtual machine" and "Show virtual hardware details".
>
> Also, selecting the "Show virtual hardware details"
14 matches
Mail list logo
