[Piuparts-devel] new tests stretch-rcmd, jessie2stretch-rcmd?

[Holger Levsen]

On Mon, Jan 16, 2017 at 11:21:27AM +0100, Andreas Beckmann wrote:
> > and else we'd ask DSA for more ressources…
> I was also thinking about cpu power ...

we can ask for that too. shall we? currently piu-slave-1 has 4 2.4ghz
operton cores with 12gigs RAM.
 
> Andreas Beckmann (11):

$ git log develop..andreas/for-holger --oneline |wc -l
24

should I pick them all?

>       reschedule_piuparts_tests: add --dryrun option
>       p: run panic handlers in reverse order
>       reschedule_oldest_logs: report idle state
>       p: ignore /etc/php/7.0/ and some subdirs
>       p: check before unmounting /proc/sys/fs/binfmt_misc
>       p.conf: [stretch-rcmd]
>       p.conf: [jessie2stretch-rcmd]
>       p.conf: [stretch-security]
>       p.conf: [stretch-pu]
>       p.conf: [stretch2proposed]
>       p.conf: [stretch-proposed]
> 
> stretch-proposed is disabled (like any -proposed)
> 
> stretch2proposed is disabled and should be enabled after release
> (seeded with pass logs from a rerun of stretch after release)
> 
> *-rcmd should be seeded with the pass logs from their respective
> non-rcmd counterparts and all logs should be marked for recycling
> immediately (s.t. they are gradually rebuilt and do not block recycling
> of other sections during their initial testing)
> 
> -pu and -security can be enabled right now, they will be just (mostly)
> empty until release

all cool, except the above question… the diff also looks fine IMO :)

-- 
cheers,
	Holger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 811 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/piuparts-devel/attachments/20170117/e3ddc96e/attachment.sig>