Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/389#issuecomment-40448460
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/411#discussion_r11620940
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -678,7 +678,7 @@ private[spark] class BlockManager(
case
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/411#issuecomment-40448496
Jenkins, add to whitelist.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/389#issuecomment-40448600
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/389#issuecomment-40448594
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/411#issuecomment-40448662
Jenkins, add to whitelist.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/411#issuecomment-40448808
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/391#issuecomment-40449078
Jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/410#discussion_r11621180
--- Diff: core/src/main/scala/org/apache/spark/Partitioner.scala ---
@@ -89,12 +89,14 @@ class HashPartitioner(partitions: Int) extends
Partitioner {
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/411#discussion_r11621270
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -678,7 +678,7 @@ private[spark] class BlockManager(
case
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/411#issuecomment-40451066
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14137/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/410#issuecomment-40451062
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/411#issuecomment-40451060
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/410#issuecomment-40451063
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14135/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/411#issuecomment-40451067
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/389#issuecomment-40451065
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14136/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/391#issuecomment-40451261
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/409#issuecomment-40451260
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/391#issuecomment-40451262
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14139/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/409#issuecomment-40451263
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14138/
---
If your project
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/363#issuecomment-40451813
I've merged this. Thanks @ahirreddy - cool stuff!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/408#issuecomment-40451991
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/408#issuecomment-40452091
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/408#issuecomment-40452101
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/353#issuecomment-40452444
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user ahirreddy commented on the pull request:
https://github.com/apache/spark/pull/363#issuecomment-40452665
Awesome, thanks!â
Sent from Mailbox for iPhone
On Tue, Apr 15, 2014 at 12:16 AM, asfgit notificati...@github.com wrote:
Closed #363 via
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/391#issuecomment-40452638
Thanks Sandeep! I've merged this in.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/353#issuecomment-40452733
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/412
Make distribution
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark make_distribution
Alternatively you can review and apply these
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/412#issuecomment-40453310
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/411#issuecomment-40453437
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14140/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/411#issuecomment-40453434
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/413#issuecomment-40454904
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/413#issuecomment-40460591
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/413#issuecomment-40467603
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/413#issuecomment-40467611
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-40470083
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-40470091
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/413#issuecomment-40473966
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user tmyklebu commented on a diff in the pull request:
https://github.com/apache/spark/pull/407#discussion_r11631197
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/recommendation/ALS.scala ---
@@ -167,11 +169,24 @@ class ALS private (
this.numBlocks
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-40475281
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user tmyklebu commented on a diff in the pull request:
https://github.com/apache/spark/pull/407#discussion_r11631405
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/recommendation/ALS.scala ---
@@ -96,6 +97,7 @@ class ALS private (
private var lambda: Double,
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/413#issuecomment-40478717
Different unrelated failures each time. One more roll of the dice.
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/372#issuecomment-40482466
@mengxr Nice one, that is music to my ears. I just suggest that if you
agree, to mark a few more of these parts of MLlib as Experimental in order to
give you the freedom
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/414
improve the readability of SparkContext.scala
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark SparkContext
Alternatively you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/415#issuecomment-40489083
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
GitHub user willb opened a pull request:
https://github.com/apache/spark/pull/415
SPARK-1501: Ensure assertions in Graph.apply are asserted.
The Graph.apply test in GraphSuite had some assertions in a closure in
a graph transformation. As a consequence, these assertions never
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/415#issuecomment-40489064
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-40491073
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-40491050
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
GitHub user techaddict opened a pull request:
https://github.com/apache/spark/pull/416
SPARK-1462: Examples of ML algorithms are using deprecated APIs
This is a work in progress any comments are welcome. This will also fix
SPARK-1464: Update MLLib Examples to Use Breeze.
You can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/416#issuecomment-40495701
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/415#issuecomment-40499267
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/415#issuecomment-40499268
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14148/
---
If your project
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/402#issuecomment-40501557
@manishamde Thanks for writing decision tree documentation! There are some
minor issues, but not worth another iteration. Do you mind me merging this
first and then making
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/396#discussion_r11642707
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/YarnSparkHadoopUtil.scala
---
@@ -17,10 +17,19 @@
package
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/416#issuecomment-40502368
@techaddict Thanks for work on this JIRA! Since we try to hide breeze types
in MLlib, I'm not sure whether we should use breeze vectors directly in
examples. We might
Github user techaddict commented on the pull request:
https://github.com/apache/spark/pull/416#issuecomment-40502741
@mengxr Ya i was thinking that too, as eventually we'll need function's
like squaredDist(in KMeans Examples) implemented in mllib.
---
If your project is set up for
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-40502679
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/407#discussion_r11643032
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/recommendation/ALS.scala ---
@@ -167,11 +169,24 @@ class ALS private (
this.numBlocks
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/407#discussion_r11643157
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/recommendation/ALS.scala ---
@@ -96,6 +97,7 @@ class ALS private (
private var lambda: Double,
Github user techaddict commented on the pull request:
https://github.com/apache/spark/pull/416#issuecomment-40506793
@srowen i think we need to implements some additional function's to
`linalg.Vector` like squaredDist (supported by `util.Vector`)
---
If your project is set up for
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/417
Loads test tables when running sbt hive/console without HIVE_DEV_HOME
When running Hive tests, the working directory is `$SPARK_HOME/sql/hive`,
while when running `sbt hive/console`, it becomes
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/415#issuecomment-40510777
lgtm. merged. thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/18#issuecomment-40514510
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/18#issuecomment-40514490
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/402#issuecomment-40515218
Looks good - thanks I've merged this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/417#issuecomment-40515442
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/417#issuecomment-40515443
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14150/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/418#issuecomment-40516161
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/418#issuecomment-40516180
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/418#issuecomment-40516364
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14152/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/418#issuecomment-40516363
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/418
Generalize pattern for planning hash joins.
This will be helpful for
[SPARK-1495](https://issues.apache.org/jira/browse/SPARK-1495) and other cases
where we want to have custom hash join
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/417#issuecomment-40517020
This change seems reasonable. I think we should leave `HIVE_DEV_HOME`
though. The point is to easily allow you to override the built in tests when
we want to upgrade
Github user dbtsai closed the pull request at:
https://github.com/apache/spark/pull/353
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user xgong commented on the pull request:
https://github.com/apache/spark/pull/396#issuecomment-40518846
@tgravescs Would you mind to review this again ? Thanks
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/402
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/18#issuecomment-40523303
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14151/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/18#issuecomment-40523300
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/18#issuecomment-40523420
I merged master in and fixed the conflicts, it should be good to merge now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/396#discussion_r11653067
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/YarnSparkHadoopUtil.scala
---
@@ -73,4 +81,61 @@ object YarnSparkHadoopUtil {
def
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/30#discussion_r11653646
--- Diff: python/pyspark/context.py ---
@@ -130,6 +130,13 @@ def __init__(self, master=None, appName=None,
sparkHome=None, pyFiles=None,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/407#issuecomment-40525624
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/407#issuecomment-40525634
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user tmyklebu commented on a diff in the pull request:
https://github.com/apache/spark/pull/407#discussion_r11653978
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/recommendation/ALS.scala ---
@@ -167,11 +169,24 @@ class ALS private (
this.numBlocks
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-40526721
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/30#issuecomment-40527887
@sryza I think this is looking good. I played around with this on a local
yarn install and it worked. The only points are twofold. Could we ditch
requiring SPARK_JAR? I'm
Github user sryza commented on a diff in the pull request:
https://github.com/apache/spark/pull/396#discussion_r11655050
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/YarnSparkHadoopUtil.scala
---
@@ -73,4 +81,61 @@ object YarnSparkHadoopUtil {
def
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/413#issuecomment-40529664
Thanks for looking at this! To add this to the test harness you can augment
`dev/scalastyle` with two additional checks:
```
SPARK_YARN=true sbt/sbt
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/413#issuecomment-40532258
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/413#issuecomment-40532267
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/408#issuecomment-40532862
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/407#issuecomment-40533842
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/407#issuecomment-40533843
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14153/
---
If your project
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/417#issuecomment-40534041
@pwendell, this can be merged. No reason not to include in 1.0 as well.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/408#issuecomment-40534045
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/413#issuecomment-40539374
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/413#discussion_r11665116
--- Diff: dev/scalastyle ---
@@ -18,6 +18,10 @@
#
echo -e q\n | sbt/sbt clean scalastyle scalastyle.txt
+# Check style with YARN alpha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/419#issuecomment-40551810
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
1 - 100 of 136 matches
Mail list logo
