[Piuparts-devel] splitting up the daily processing to allow concurrency

[Andreas Beckmann]

On 10/10/2017 04:02 PM, Holger Levsen wrote:
> On Mon, Oct 09, 2017 at 05:46:47PM +0200, Andreas Beckmann wrote:
>>>> b035a50b8 introduce scripts-long-grown
>>>
>>> but stopped here… what are "long grown" scripts? the comments in the new
>>> script also don't explain the name…
>>
>> The followup commit might make it clear where they are used.
> 
> not really, if you mean 664810fc9
>  
>> I'm going to call everything in *my* config that has a (wildcard) 222 in
>> it a "long grown upgrade test" (better naming welcome). 
> 
> I'd suggest something if I'd understand what you mean :/
> 
> "lange gewachsener upgrade test" also doesnt make sense in German too me.
> 
> Can you please again try to explain what it is?

How would you describe a test upgrading from lenny to squeeze to
wheezy to jessie to stretch to buster?

While discussing naming ... I reorderd the pacthes

c3104d1be lib/db: Package: add accessors name(), version(), test_versions()
7bd90a50d lib/db: Package: use test_versions() in all places referring to a piuparts test
2b6a5aafe lib/db: Package: set test_versions to the version in the final distro
e8dbfff77 lib/db: use the actual package versions for resolving the "outdated" state
99af32152 p-r: acquire a global "report.lock"
90cc44c32 p-r: aquire master.lock for the current section (blocking)
ceba56426 dwke: acquire a global "dwke.lock"
8656ef8d8 dwke: acquire master.lock for the current section (blocking)
a40579ad9 p-a: aquire master.lock for the current section (blocking)
4f9378c9e p-a: process all sections
c9ccbc2ab split the generate_daily_report cronjob
5ad9fe6fe remove master-bin/report_newly_bugged_packages
c6b6f37a1 Revert "master-bin/report_untestable_packages.in: only act on sections with precedence < 100."
a4d328314 introduce scripts-long-grown
ca0b3d132 p.conf.anbe: use scripts-long-grown