yeah, totally weird.
i'm actually going to take this moment and clean up the build scripts
for both of these jobs. there's a lot of years-old cruft that i'll
delete and make things more readable.
On Sun, Dec 8, 2019 at 7:50 PM Sean Owen wrote:
>
> Hm, so they look pretty similar except for
Hm, so they look pretty similar except for minor differences in the
actual script run. Is there any reason this should be different? Would
it be reasonable to try making the 'new' one work like the 'old' one
if the former isn't working?
But I still can't figure out why it causes the same odd
++yin huai for more insight in to the NewSparkPullRequestBuilder job...
tbh, i never (or still) really understand the exact use for that job,
except that it's triggered by https://spark-prs.appspot.com/
shane
On Wed, Dec 4, 2019 at 3:34 PM Sean Owen wrote:
>
> BTW does anyone know why there
BTW does anyone know why there are two PR builder jobs? I'm confused
about why different ones would execute.
Yes I see NewSparkPullRequestBuilder failing on a variety of PRs.
I don't think it has anything to do with Hive; these PRs touch
different parts of code but all not related to this
Hi, Sean.
It seems that there is no failure on your other SQL PR.
https://github.com/apache/spark/pull/26748
Does the sequential failure happen only at `NewSparkPullRequestBuilder`?
Since `NewSparkPullRequestBuilder` is not the same with
`SparkPullRequestBuilder`,
there might be a root
I'm seeing consistent failures in the PR builder when touching SQL code:
https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/4960/testReport/
org.apache.spark.sql.hive.thriftserver.SparkMetadataOperationSuite.Spark's
own GetSchemasOperation(SparkGetSchemasOperation)14 ms2
