Strange, looks like Rietveld did not calculate the patch diff for some reason.

Here is the patch of regress-2825.js (it is empty): https://codereview.chromium.org/2480283002/patch/1/100009
Here is the patch of regress-269.js (it looks right): https://codereview.chromium.org/2480283002/patch/1/90011

It is not obvious to me why it would fail to calculate the inverted patch :/

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/39b86ad453e795db162c84021793f209d3efc6e4

commit 39b86ad453e795db162c84021793f209d3efc6e4
Author: jgruber <jgruber@chromium.org>
Date: Mon Nov 07 15:46:31 2016

Manually complete failed revert

The revert somehow lost the contents of regress-2825.js.

NOTRY=true
NOPRESUBMIT=true
NOTREECHECKS=true
BUG= chromium:662928 

Review URL: https://codereview.chromium.org/2483863002 .

Cr-Commit-Position: refs/heads/master@{#40806}

[modify] https://crrev.com/39b86ad453e795db162c84021793f209d3efc6e4/test/mjsunit/regress/regress-2825.js

Maybe related: regress-2825.js has various line endings.

[...]
// Do not edit this file with an editor that replaces \r with \r\n.
// Variable definitions for i0 through i3 are each terminated with \r.
function f() {
  var i0 = 0;^M  var i1 = 1;^M  var i2 = 2;^M  var i3 = 3;
  var j0 = 0;
[...]

$ hexdump -c test/mjsunit/regress/regress-2825.js
[...]
0000160   (   )       {  \n           v   a   r       i   0       =    
0000170   0   ;  \r           v   a   r       i   1       =       1   ;
0000180  \r           v   a   r       i   2       =       2   ;  \r    
0000190       v   a   r       i   3       =       3   ;  \r  \n

In fact, when trying to manually fix the revert (over the web interface), the patch diff fails at exactly the affected lines: https://codereview.chromium.org/2483863002/

Rietveld is already known to not handle Windows line endings.