On 6/5/21 3:18 PM, Andrew Hewus Fresh wrote: > On Sat, May 29, 2021 at 08:05:56PM -0400, Ricardo Signes wrote: >> I was looking at https://perl5.test-smoke.org/ earlier today, and >> looking at some of our branches, and just sort of generally looking >> around earlier, and I came to wonder: Is anybody still smoking the >> smoke-me branches? > > When I set up my sparc64 smoker with Test::Smoke I couldn't figure out > how to make it do smoke-me branches. The first entry in smokecurrent.gitbranch is what get's smoked. Personally, I start all smoke-test runs manually, so I simply manually set the first line to the branch I want to smoke. Others may be able to tell you about setting up cron jobs to smoke all branches upon their first appearance. I did ask in #perl-qa for > direction but still wasn't able to figure out how to make it do that. > There is also #smoke >> They were useful. Can someone who has been paying attention the whole >> time fill me (and us) in as to their status? > > If someone tells me how, I can make my smoker do it. > > My smoker has lots of fairly slow processors, so if it was possible, I > would love to be able to do a smoke where I do all the different builds > there in parallel, but (I can't recall the details at the moment) there > was some collision with a file in /tmp or someplace that meant parallel > perl tests didn't work. > I have never attempted parallel runs but, yes, that would be a nice feature. The Test-Smoke codebase is large. I have never been able to hold it in my head enough to figure out the complete workflow or to attempt more than modest refactorings. I suspect a lot of it is superfluous or outdated, but I can't be sure which parts. Thank you very much. Jim KeenanThread Previous | Thread Next