beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [beam-site] 01/01: Prepare repository for deployment.
Date Wed, 12 Jul 2017 18:09:39 GMT
This is an automated email from the ASF dual-hosted git repository.

mergebot-role pushed a commit to branch asf-site
in repository

commit 7ca12569914169a6adf1d0646dc34c30907e1b19
Author: Mergebot <>
AuthorDate: Wed Jul 12 18:09:36 2017 +0000

    Prepare repository for deployment.
 content/contribute/testing/index.html | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/content/contribute/testing/index.html b/content/contribute/testing/index.html
index ac4aec0..044357a 100644
--- a/content/contribute/testing/index.html
+++ b/content/contribute/testing/index.html
@@ -471,11 +471,6 @@ functionality, but runner functionality as well. They are more lightweight
 a traditional end-to-end test and, because of their well-scoped nature, provide
 good signal as to what exactly is working or broken against a particular runner.</p>
-<p>The name “ValidatesRunner” is an artifact of when Beam was still the Google
-Cloud Dataflow SDK and <a href="">will
-changing</a> to something more
-indicative of its use in the coming months.</p>
 <h3 id="e2e">E2E</h3>
 <p>End-to-End tests are meant to verify at the very highest level that the Beam

To stop receiving notification emails like this one, please contact
"" <>.

View raw message