[APM] Run precommit tasks sequentially

Jest seems to panic when running in parallel with the other tasks, possibly due to resource issues. Running the tasks sequentially looks to be more reliable.
elastic · Apr 8, 2021 · cc81252 · cc81252
1 parent 7984745
commit cc81252
Showing 1 changed file with 16 additions and 16 deletions.
diff --git a/x-pack/plugins/apm/scripts/precommit.js b/x-pack/plugins/apm/scripts/precommit.js
@@ -28,19 +28,8 @@ const testTsconfig = resolve(root, 'x-pack/test/tsconfig.json');
 const tasks = new Listr(
   [
     {
-      title: 'Jest',
-      task: () =>
-        execa(
-          'node',
-          [
-            resolve(__dirname, './jest.js'),
-            '--reporters',
-            resolve(__dirname, '../../../../node_modules/jest-silent-reporter'),
-            '--collect-coverage',
-            'false',
-          ],
-          execaOpts
-        ),
+      title: 'Lint',
+      task: () => execa('node', [resolve(__dirname, 'eslint.js')], execaOpts),
     },
     {
       title: 'Typescript',
@@ -72,11 +61,22 @@ const tasks = new Listr(
         ),
     },
     {
-      title: 'Lint',
-      task: () => execa('node', [resolve(__dirname, 'eslint.js')], execaOpts),
+      title: 'Jest',
+      task: () =>
+        execa(
+          'node',
+          [
+            resolve(__dirname, './jest.js'),
+            '--reporters',
+            resolve(__dirname, '../../../../node_modules/jest-silent-reporter'),
+            '--collect-coverage',
+            'false',
+          ],
+          execaOpts
+        ),
     },
   ],
-  { exitOnError: true, concurrent: true }
+  { exitOnError: true, concurrent: false }
 );
 
 tasks.run().catch((error) => {