Issue metadata
Sign in to add a comment
|
CQing not yet landed but recently rebased CL fails with spurious patch application failure
Reported by
k.dev...@samsung.com,
Mar 17 2017
|
||||||||||||||||||||||
Issue descriptionPlease explain below why you believe CQ is not working. After a I fixed some unit-test errors reported by few trybots, I fixed the unittests, compiled the unit test locally and submitted for CQ-Dryrun again and this time all bots fail- with 'Patch failure', though the final failure does not seem to be from the changes in the patch. The failure looks like the following: I noticed this 2 times sofar March 17th & March 10th or so. on the patch https://codereview.chromium.org/2684933003/ --------------------------------------------------------------------------- third_party/android_tools/google_play_services_basement_java.interface.jar:lib.javava/third_party/gvr-android-sdk/gvr_common_java.interface.jar -sourcepath : -../../chrome/android/java/src/org/chromium/chrome/browser/ntp/snippets/SnippetsBridge.java:295: error: method references are not supported in -source 1.7 boolean hasFetchAction = additionalAction == ContentSuggestionsAdditionalAction::FETCH; ^ (use -source 8 or higher to enable method references) 1 error ---------------------------------------------------------------------------
,
Mar 20 2017
,
Mar 21 2017
k.devara@samsung.com can you provide more info as requested in comment #1?
,
Mar 23 2017
marking wontfix, please re-open with more details. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by tandrii@chromium.org
, Mar 20 2017