Test Keeping NaCl plugins used in app background pages alive when active.

ppapi/tests/extensions/extensions.gyp

 # Copyright (c) 2013 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 {
   'includes': [
     '../../../ppapi/ppapi_nacl_test_common.gypi',
   ],
   'targets': [
     {
@@ skipping 11 matching lines @@
           '<(DEPTH)/ppapi/tests/test_utils.h',
         ],
         'test_files': [
           'socket/controller.js',
           'socket/index.html',
           'socket/main.js',
           'socket/manifest.json',
         ],
       },
     },
+    {
+      'target_name': 'ppapi_tests_extensions_background_keepalive',
+      'type': 'none',
+      'variables': {
+        'nexe_target': 'ppapi_tests_extensions_background_keepalive',
+        'build_newlib': 1,
+        'build_glibc': 0,

[Mark Seaborn, 2013/12/18 21:07:57]

Is there a specific reason to disable this on glibc and PNaCl?  Maybe this could
use a comment.

[scheib, 2013/12/19 01:31:37]

Comment added.

The AppBackgroundPageNaClTest fixture only uses the newlib build. I don't think
there's a reason to span the test over all build types. 

+        'build_pnacl_newlib': 0,
+        'nexe_destination_dir': 'test_data/ppapi/tests/extensions/background_keepalive',
+        'sources': [
+          'background_keepalive/background.cc',
+        ],
+        'test_files': [
+          'background_keepalive/background.js',
+          'background_keepalive/manifest.json',
+        ],
+      },
+    },
   ],
 }