Heh, where Travis used to be the slow CI, Circle now takes 2x as long as Travis. Travis used to be ~1:00, now Travis is ~0:30. Circle used to be ~0:30, now, Circle is ~1:00.
> Bad keyword in body, bad keyword in title, bad keyword in username, url in title ---------- Title - Position 1-4: >>> Username - Position 1-4: >>> Body - Position 1-4: >>> Title - Position 10-36: http://www.tokoterbaik.com
> Pattern-matching website in body, pattern-matching website in title, pattern-matching website in username ---------- Title - Position 6-20: workoutsup.com Username - Position 6-20: workoutsup.com Body - Position 6-20: workoutsup.com
@NormalHuman CircleCI shows the time per build step, and that tells me it's only ~2 seconds to do the actual testing, so it's probably the setup-and-collect-test-data part that takes long.
I had an awesome idea on how to better detect plagiarism in Tag Wikis (though, it'd be about a week behind because I can't find an API end point that just lets me query based on new tags). The problem is, Google gets angry if you use their search API more than 100 times a day.
I'm pretty sure, I've gotten my IP blocked for the next 24 hours.
Whoops
{'responseData': None, 'responseDetails': 'Quota Exceeded. Please see http://code.google.com/apis/websearch', 'responseStatus': 403}
Even more annoying...that URL they give you to check quotas returns a 404
