I'm marking it as Infra-Git since it's a VCS-related issue. cc'ing mmoss in case he knows more.

I gather at some point git became the source of truth for this repo, but the svn repo was never deleted:

https://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/webrtc/manual/

I think the only fix here is to actually delete the old svn repo.

Right, can we please do that? Enough time must have passed to ensure this doesn't break old users of it.

You could eventually just drop everything and check in a README file instead.
Even better would be if it's possible to just redirect the viewvc-URLs to some landing page explaining that the SVN repo is now replaced by Git.
The over-ambitious solution would be to URL-rewrite the old links to map to Gitiles, but AFAIK it's not possible to serve the content directly from Gitiles (one would end up at viewing the actual HTML source in this case, which of course is fine).

Renaming to something more generic since this is not specific to WebRTC.

I wasn't able to find any old cleanup bug to reference for this.

I don't think shutting down any of those things is an option, since svn is still the source of truth for a bunch of chrome-internal repos.  And I have no idea about redirects. That might be an infra-labs thing, something done at the networking level.

Ah, I forgot all the repos are using the same Subversion server (reverting topic change).

So, is it possible for us to perform a Subversion commit that removes everything below https://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/webrtc/ ?
I'm suspecting that repo is read-only? In that case I guess we need to get assistance from Infra-Labs setting up some networking redirect based on the URL.

Oh, yeah, it probably is read-only. I've never really dealt with the svn servers, so I don't know how to work around that. Maybe vadimsh?

(removing infra-git, since this is nothing to do with git repos at this point, and vcs issues don't generalize to infra-git issues)

Sounds like this is now in labs' hands. See comment #7.

Labs: any comment on if this is doable?

No, we can't serve redirects from src.chromium.org (nor would we want to, it would get messy fast).

So in other words there is no way to get around this problem of us having old stuff show up in Google searches like https://www.google.se/search?sourceid=chrome-psyapi2&ion=1&espv=2&ie=UTF-8&q=webrtc%20manual%20constraints.html&oq=webrtc%20manual%20constraints.html&aqs=chrome..69i57j69i64.3600j0j7

Maybe src.chromium.org could at least put a robots.txt in the root?

+dba to help answer question on comment #7

This will be "fixed" once https://bugs.chromium.org/p/chromium/issues/detail?id=600451 is completed (which should be soon) 

I believe this is because we left it as RO for now.

Oh, somehow I was never CC'd on this before. Yeah, we can trivially remove the read-only restriction, land a sentinel commit saying "go look for these files in Git", and then re-add the read-only restriction.

https://src.chromium.org/svn/trunk/src/chrome/test/data/webrtc/manual/