You know, I'm glad I'm running the tinderbox from my home and not from a co-location because I would have *a bit of a hard time* to explain why I've been fetching porn videos in such a case. Check the attached build log. Please, just restrict the tests or put it under an offensive USE flag or something, this doesn't look any right at all.
Created attachment 213992 [details] Build log
Actually, I'd suggest adding a local USE flag for each supported site (and of course clear descriptions for each one). Also as a side note, I think any business locations would be more concerned about the hundreds of MB of video downloads you did than exactly which ones they were. Consider not using the test feature in a formal environment :P
Point is that the whole point of running the tinderbox is checking the testsuites. And all the tests *have* to be runnable in formal environments.
dont run the tests then. upstream specifically added support to cclive to fetch porn videos. there's nothing offensive in having support compiled into the program itself.
This package tests require by default internet connection to be working. How else would you test if the api changed for the site to test fetching. If those tests are bad due to their nature how about adding useflag tests and ewarn user that he really needs to have working net connection for this thing to work?
Bumped to latest 0.5.7 and added offensive useflag to switch between fetching p0rn or not. and created 2 reports: http://code.google.com/p/cclive/issues/detail?id=19 http://code.google.com/p/cclive/issues/detail?id=20
Looks like this is fixed...
