Trying to update FeedRefreshTaskTest.java, I ran into a problem. I wanted to add an annotation such that the file would look like

@RunWith(ChromeJUnit4ClassRunner.class)
@CommandLineFlags.Add(ChromeSwitches.DISABLE_FIRST_RUN_EXPERIENCE)
@Features.EnableFeatures(ChromeFeatureList.INTEREST_FEED_CONTENT_SUGGESTIONS)
public class FeedRefreshTaskTest {

However, after "git cl format" (which was forced by PRESUMIT), it looked like

@RunWith(ChromeJUnit4ClassRunner.class)
@CommandLineFlags
        .Add(ChromeSwitches.DISABLE_FIRST_RUN_EXPERIENCE)
        @Features.EnableFeatures(ChromeFeatureList.INTEREST_FEED_CONTENT_SUGGESTIONS)
        public class FeedRefreshTaskTest {

While this looks bad, it's actually much worse. When we compile the class, we get some sort of forced lint error!

  File "../../build/android/gyp/javac.py", line 622, in <module>
    sys.exit(main(sys.argv[1:]))
  File "../../build/android/gyp/javac.py", line 618, in main
    add_pydeps=False)
  File "/usr/local/google/home/skym/chromium/clankium/src/build/android/gyp/util/build_utils.py", line 597, in CallAndWriteDepfileIfStale
    pass_changes=True)
  File "/usr/local/google/home/skym/chromium/clankium/src/build/android/gyp/util/md5_check.py", line 87, in CallAndRecordIfStale
    function(*args)
  File "/usr/local/google/home/skym/chromium/clankium/src/build/android/gyp/util/build_utils.py", line 582, in on_stale_md5
    function(*args)
  File "../../build/android/gyp/javac.py", line 610, in <lambda>
    classpath_inputs, classpath),
  File "../../build/android/gyp/javac.py", line 388, in _OnStaleMd5
    _CreateInfoFile(java_files, options, srcjar_files, javac_generated_sources)
  File "../../build/android/gyp/javac.py", line 249, in _CreateInfoFile
    'Chromium java files must only have one class: {}'.format(source))
AssertionError: Chromium java files must only have one class: ../../chrome/android/javatests/src/org/chromium/chrome/browser/feed/FeedRefreshTaskTest.java
ninja: build stopped: subcommand failed.

Essentially stopping anyone from having a java test class with 2+ annotations. If we remove either of the two annotations, then the weird formatting goes away.