I've gone and built a naive version of this for my own uses. It doesn't yet hook into cpanm-reporter but i don't think it'd be hard to do. It's intending to take a --module or --cpanfile to start from and works its way through the dependency tree (fetches it all with cpanm --showdeps) and then tests them with perlbrew exec --with ... so that the script can run in a stable perl install while testing current blead/git easily. I'll toss it up on github if there's any big call for it (otherwise it'll just live publicly on my server). https://gitea.simcop2387.info/simcop2387/treedeps On Sun, Mar 26, 2017 at 8:39 PM, Kent Fredric <kentfredric@gmail.com> wrote: > On 27 March 2017 at 16:10, Dan Collins <dcollinsn@gmail.com> wrote: > > I've had a chance to make sure that this test environment isn't horribly > > broken... > > > Yeah, there's enough broken you sort of need a double-testing system. > > Start with =0 , and then upon hitting a failure, retry with =1 ... > while paying care > not to let the =1 bleed into children in the recursive step. > > eg: > > 1. Install X with UNSAFE_INC=0 > 2. Configure fails? > 1. Report N/A Fail > 2. Generate META.JSON with UNSAFE_INC=1 > 3. Installdeps with UNSAFE_INC=0 > 4. Run tests with UNSAFE_INC=0 > 5. Tests Fail? > 1. Report FAIL > 2. Re-run tests with UNSAFE_INC=1 > 3. Report Test result > > I don't know how to make my tools do this automatically so I've been > doing it manually and filing bugs, to fill the gaps in automation. > > > > -- > Kent > > KENTNL - https://metacpan.org/author/KENTNL >Thread Previous | Thread Next