| Subject: | fork() before reporting tests |
When installing a big wad of CPAN modules, reporting the test results
slows things down. I figured it was the process of sending an email,
but it seems even the new Metabase system has a delay. Not nearly as
bad as it was with email, but this can get really bad on a dodgy network
the result being that for big builds I'll turn it off.
Since reporting a test has no effect on the install process it could be
done in the background while CPAN.pm goes about its business.
There's no need to inform the user of a successful report, but telling
them about a problem becomes a... problem. How the subprocess
communicates with the parents is a SMOP, but wedging the information
into the CPAN interface isn't. Any problems could be reported as part
of the end-of-command summary that normally reports any problems with
installing modules. This would require the end of summary waiting for
the children to finish which, in the worst case, is no worse than were
it is now.
Good idea?