From 8f6a96c2130f185dd2fe49e72a57f66dc89e7e7d Mon Sep 17 00:00:00 2001
From: Abhishek Arya <inferno@chromium.org>
Date: Wed, 15 Feb 2017 18:27:38 -0800
Subject: [PATCH] Speculative fix for timeouts

[Pipeline] timeout
Timeout set to expire in 4 hr 0 min
[Pipeline] {
Several projects stuck on timeouts around evening time.

[Pipeline] node
Still waiting to schedule task
Waiting for next available executor
Cancelling nested steps due to timeout
---
 infra/libfuzzer-pipeline.groovy | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/infra/libfuzzer-pipeline.groovy b/infra/libfuzzer-pipeline.groovy
index d063a1944..e8b4ee752 100644
--- a/infra/libfuzzer-pipeline.groovy
+++ b/infra/libfuzzer-pipeline.groovy
@@ -42,7 +42,7 @@ def call(body) {
     def date = java.time.format.DateTimeFormatter.ofPattern("yyyyMMddHHmm")
         .format(java.time.ZonedDateTime.now(java.time.ZoneOffset.UTC))
 
-    timeout(time: 4, unit: 'HOURS') {
+    timeout(time: 6, unit: 'HOURS') {
     node {
         def workspace = pwd()
         def srcmapFile = "$workspace/srcmap.json"