[beam] branch asf-site updated: Publishing website 2018/10/26 18:26:17 at commit c7adb01

Fri, 26 Oct 2018 11:26:48 -0700 

This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/beam.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new e1ef435  Publishing website 2018/10/26 18:26:17 at commit c7adb01
e1ef435 is described below

commit e1ef435c15dee9f207255287cdcefdee588aea09
Author: jenkins <bui...@apache.org>
AuthorDate: Fri Oct 26 18:26:18 2018 +0000

    Publishing website 2018/10/26 18:26:17 at commit c7adb01
---
 .../contribute/precommit-triage-guide/index.html   |  30 ++++++--------------
 .../images/precommit_dashboard.png                 |  31 +++++++++++++++++++++
 .../images/precommit_durations.png                 | Bin 45673 -> 0 bytes
 3 files changed, 39 insertions(+), 22 deletions(-)

diff --git 
a/website/generated-content/contribute/precommit-triage-guide/index.html 
b/website/generated-content/contribute/precommit-triage-guide/index.html
index ddbba37..4404e67 100644
--- a/website/generated-content/contribute/precommit-triage-guide/index.html
+++ b/website/generated-content/contribute/precommit-triage-guide/index.html
@@ -210,7 +210,7 @@
   <li><a href="#what-are-fast-pre-commits">What are fast pre-commits?</a></li>
   <li><a href="#determining-slowness">Determining Slowness</a>
     <ul>
-      <li><a href="#notebook">Notebook</a></li>
+      <li><a href="#pre-commit-dashboard">Pre-commit Dashboard</a></li>
     </ul>
   </li>
   <li><a href="#triage-process">Triage Process</a></li>
@@ -270,31 +270,17 @@ the Jenkins queue + the actual time it spends running.</p>
   <li>Pre-commit jobs are timing out after 30 minutes. This can be determined 
from
 the console log of a job.</li>
   <li>Pre-commits aren’t timing out, but the total wait time for pre-commit 
results
-is &gt;30m. This can be determined using a Jupyter notebook.</li>
+is &gt;30m.</li>
 </ol>
 
-<h3 id="notebook">Notebook</h3>
+<h3 id="pre-commit-dashboard">Pre-commit Dashboard</h3>
 
-<p>The Beam repo contains a <a 
href="https://github.com/apache/beam/tree/master/.test-infra/jupyter";>Jupyter
-notebook</a> named
-<code class="highlighter-rouge">precommit_job_times.ipynb</code> that can be 
used to gather and visualize statistics
-about pre-commit running times.</p>
+<p>The Beam Community Metrics site contains a <a 
href="http://104.154.241.245/d/_TNndF2iz/pre-commit-tests";>Pre-Commit
+Tests</a> dashboard showing
+job timing trends. You can modify the time window (defaults to 7 days) or 
filter
+down to a specific test suite by clicking on it.</p>
 
-<p>Run the notebook. It should output a table with running times. The numbers 
in
-the column <code class="highlighter-rouge">totalDurationMinutes_all</code> and 
the rows with a <code class="highlighter-rouge">job_name</code> like <code 
class="highlighter-rouge">4
-weeks 95th</code> contain the target numbers for determining slowness.
-If any of these numbers are above 30, triaging is required.</p>
-
-<h4 id="example">Example</h4>
-<p>Here’s an example table of running times:</p>
-
-<p><img src="/images/precommit_durations.png" alt="example pre-commit duration 
table" /></p>
-
-<p>(Note that this example was created when pre-commits did not have 30m 
timeouts.)</p>
-
-<p>In this example, Go pre-commits are taking approximately 14 minutes, which 
is
-fast. Java and Python pre-commits are taking 78 and 32 minutes respectively,
-which is slow. Both Java and Python pre-commits require triage.</p>
+<p><img src="/images/precommit_dashboard.png" alt="example pre-commit duration 
dashboard" /></p>
 
 <h2 id="triage-process">Triage Process</h2>
 
diff --git a/website/generated-content/images/precommit_dashboard.png 
b/website/generated-content/images/precommit_dashboard.png
new file mode 100644
index 0000000..49e4065
--- /dev/null
+++ b/website/generated-content/images/precommit_dashboard.png
@@ -0,0 +1,31 @@
+<!DOCTYPE html>
+<html lang="en">
+  <head>
+  <meta charset="utf-8">
+  <meta name="robots" content="noindex">
+  <title>Sign in - Google Accounts</title>
+  <meta http-equiv="refresh" content="1; 
url=https://www.google.com/accounts/AccountChooser?hd=google.com&amp;continue=https%3A%2F%2Fappengine.google.com%2F_ah%2Fconflogin%3Fcontinue%3Dhttps%3A%2F%2Fscreenshot.googleplex.com%2Fu5CALdM0vvL.png&amp;service=ah";></meta>
+  </head>
+  <body >
+  <form id="hiddenget" 
action="https://www.google.com/accounts/AccountChooser?hd=google.com&amp;continue=https%3A%2F%2Fappengine.google.com%2F_ah%2Fconflogin%3Fcontinue%3Dhttps%3A%2F%2Fscreenshot.googleplex.com%2Fu5CALdM0vvL.png&amp;service=ah";
 method="get">
+  <noscript>
+  You should turn on Javascript support.
+  <input type="submit" id="nojssubmit" value="Continue">
+  </noscript>
+</form>
+  <script nonce="ltS697Ql5dRzrGv5NV4wXk0ybRU">
+window.onload = function() {
+  var redirectUrl = 
'https:\x2F\x2Fwww.google.com\x2Faccounts\x2FAccountChooser?hd=google.com\x26continue=https%3A%2F%2Fappengine.google.com%2F_ah%2Fconflogin%3Fcontinue%3Dhttps%3A%2F%2Fscreenshot.googleplex.com%2Fu5CALdM0vvL.png\x26service=ah';
+  var domain = 'google.com';
+  var hash = window.location.hash;
+  if (hash) {
+  var match = hash.match(/[#&]Email=([^&]+)/);
+  if (match) {
+  redirectUrl += "&Email=" + match[1] + "@" + domain;
+  }
+  }
+  window.location.replace(redirectUrl);
+};
+</script>
+  </body>
+</html>
diff --git a/website/generated-content/images/precommit_durations.png 
b/website/generated-content/images/precommit_durations.png
deleted file mode 100644
index c659677..0000000
Binary files a/website/generated-content/images/precommit_durations.png and 
/dev/null differ

Reply via email to