Andrew Donnellan <andrew.donnel...@au1.ibm.com> writes: > On 22/02/18 01:29, Thomas Petazzoni wrote: >> Unfortunately, I have no idea how we could easily test this, since >> we're using the official ozlabs.org instance. Do you think it would be >> possible to have a separate testing instance setup, which we subscribed >> to the Buildroot mailing list as well, just to check if the problem is >> fixed? Of course, we won't be using this testing instance to update the >> status of patches, but we would at least be able to verify that no >> patches are lost. >> >> What do you think? > > dja used to run a testing instance but VMs ain't free :)
I thought about spinning up a VM, but I'm not sure if it would be sufficiently equivalent to the OzLabs set up to actually hit the bug... I think hitting the issue it's due to a combination of OzLabs and Buildroot features: - how quickly the buildroot mailing list sends mail - how quickly ozlabs receives it - both in terms of mail system lag and just in terms of network locality - how many cpus ozlabs has to parallelise processing, etc I don't think I can get an OzLabs like virtual machine for very long without spending a *lot* of money. > We'll probably just backport this to ozlabs.org after this gets a bit of > review. I think this is probably the way to go, but it's worth noting that as always I'm not at OzLabs any more :) Regards, Daniel > > > -- > Andrew Donnellan OzLabs, ADL Canberra > andrew.donnel...@au1.ibm.com IBM Australia Limited _______________________________________________ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
