We should investigate if omitted RegisterJNI calls can be treated as compile-time errors. Failing that, we should at least check these calls on the CQ.

Missing RegisterJNI calls will cause compile errors for any functions which are actually tested. Unfortunately, there's always the possibility that JNI calls won't be tested on the CQ (perhaps if the classes are not easily testable). However, missing JNI registration can cause a crash on startup for chrome, so it's important to catch mistakes like these.

See go/chromepostmortem340 (internal only).

CC'ing Torne, in case he has any ideas off the top of his head on how to achieve this (although last we talked, we concluded this would be very difficult to actually fix).