I know the exact test you are talking about, but unfortunately there isn't a great way of handling what I need to test here.
The purpose of this particular test is to confirm the proper handling of a remote file. A local file:// would not properly exercise the various code paths involved.
The use of rawgit.com seemed very clever when I first implemented it, but the maneuvering of that organization (I guess they had a copyright problem for a while) has definitely caused problems with this test.
I think it would probably be better for me to print a warning along with the test if it fails, but removing the test or altering it would weaken the verification that things are working as they are supposed to.
-Kevin
On Thu Jun 12 22:11:02 2014, LXP wrote:
Show quoted text> t/embedded_style_block.t makes a remote GET request for a file that
> already exists under t/html.
>
> Since CSS::Inliner uses LWP::UserAgent internally, and LWP::UserAgent
> supports the use of file:// URLs, it should be reasonably easy to modify
> the test to retrieve that data via a file:// URL (unless code exists
> within CSS::Inliner itself which would prevent LWP from doing so).
>
> This would improve the reliability of this test, which would improve the
> CPAN Testers results. It would also marginally improve the speed of the
> test suite execution.