RESOLVED FIXED 80582
Make check-webkit-style complain about "No new tests (OOPS)" lines in changelogs
https://bugs.webkit.org/show_bug.cgi?id=80582
Summary Make check-webkit-style complain about "No new tests (OOPS)" lines in changelogs
Nat Duca
Reported 2012-03-08 02:32:43 PST
Make check-webkit-style complain about "No new tests (OOPS)" lines in changelogs
Attachments
Patch (2.97 KB, patch)
2012-03-08 02:33 PST, Nat Duca
no flags
Patch for landing (2.95 KB, patch)
2012-03-08 10:47 PST, Nat Duca
no flags
Patch (3.00 KB, patch)
2012-03-08 11:30 PST, Nat Duca
no flags
Patch for landing (2.99 KB, patch)
2012-03-09 01:58 PST, Nat Duca
no flags
Nat Duca
Comment 1 2012-03-08 02:33:09 PST
David Levin
Comment 2 2012-03-08 09:37:34 PST
Comment on attachment 130798 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=130798&action=review > Tools/Scripts/webkitpy/style/checkers/changelog.py:78 > + "Need whitespace between colon and description") I don't think this is what you want the error to say.
Nat Duca
Comment 3 2012-03-08 10:47:49 PST
Created attachment 130849 [details] Patch for landing
David Levin
Comment 4 2012-03-08 11:00:55 PST
You can re-add cq+ but I wanted to say this which I should have said before. Many times when I've seen people have this they are new and need guidance. The typical guidance is "You should remove the 'No new tests' and either add tests and list them here or explain why no new tests were possible which may be due to the fact that n'N change in behavior happened so no new tests'." Apologies for not saying this before. You may leave it as is or add something more directed like I did above.
Nat Duca
Comment 5 2012-03-08 11:24:24 PST
Great idea! I'll adjust the text accordingly. (In reply to comment #4) > You can re-add cq+ but I wanted to say this which I should have said before. > > Many times when I've seen people have this they are new and need guidance. > > The typical guidance is "You should remove the 'No new tests' and either add tests and list them here or explain why no new tests were possible which may be due to the fact that n'N change in behavior happened so no new tests'." > > Apologies for not saying this before. You may leave it as is or add something more directed like I did above.
Nat Duca
Comment 6 2012-03-08 11:30:23 PST
Nat Duca
Comment 7 2012-03-08 11:31:06 PST
Comment on attachment 130866 [details] Patch Hows this?
WebKit Review Bot
Comment 8 2012-03-08 18:34:51 PST
Comment on attachment 130866 [details] Patch Rejecting attachment 130866 [details] from commit-queue. Failed to run "['/mnt/git/webkit-commit-queue/Tools/Scripts/webkit-patch', '--status-host=queues.webkit.org', '-..." exit_code: 2 Last 500 characters of output: Kit/chromium/third_party/yasm/source/patched-yasm --revision 124103 --non-interactive --force --accept theirs-conflict --ignore-externals' in '/mnt/git/webkit-commit-queue/Source/WebKit/chromium' 48>At revision 124103. ________ running '/usr/bin/python tools/clang/scripts/update.py --mac-only' in '/mnt/git/webkit-commit-queue/Source/WebKit/chromium' ________ running '/usr/bin/python gyp_webkit' in '/mnt/git/webkit-commit-queue/Source/WebKit/chromium' Updating webkit projects from gyp files... Full output: http://queues.webkit.org/results/11898241
Nat Duca
Comment 9 2012-03-09 01:58:01 PST
Created attachment 131014 [details] Patch for landing
WebKit Review Bot
Comment 10 2012-03-09 03:13:59 PST
Comment on attachment 131014 [details] Patch for landing Clearing flags on attachment: 131014 Committed r110282: <http://trac.webkit.org/changeset/110282>
WebKit Review Bot
Comment 11 2012-03-09 03:14:04 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.