I'm getting different errors when I run on a different machine; not
quite the same. Things like:

[ERROR] Errors:
[ERROR]   JavaTfIdfSuite.tfIdf:44 » Spark Job aborted due to stage
failure: Task 0 in st...
[ERROR]   JavaTfIdfSuite.tfIdfMinimumDocumentFrequency:64 » Spark Job
aborted due to sta...

It seems like it must be env-related, but on two different environments.

What type of OS are you running on and what -P flags?

If anyone else is successfully building and running tests, I'll assume
it's env and test issues. The rest looks OK.

On Fri, Jan 18, 2019 at 6:53 PM Takeshi Yamamuro <linguin....@gmail.com> wrote:
>
> Hi, sean,
>
> I run these tests again though, these tests passed on my AWS env.
> But, I notice these streaming tests are a little flaky though...
>
>
> On Sat, Jan 19, 2019 at 1:51 AM Sean Owen <sro...@apache.org> wrote:
>>
>> The release itself looks OK. I'm getting, as before, a lot of errors
>> on the machine I'm building on. Is anyone else seeing this? if not I'm
>> going to scrap the env and try something new. Errors like:
>>
>>
>> - event ordering *** FAILED ***
>>   The code passed to failAfter did not complete within 10 seconds.
>> (StreamingQueryListenerSuite.scala:434)
>>
>> - left outer early state exclusion on right *** FAILED ***
>>   Assert on query failed: Check total state rows = List(4), updated
>> state rows = List(4): Array(1) did not equal List(4) incorrect updates
>> rows
>>
>> - left outer join with non-key condition violated *** FAILED ***
>>   == Results ==
>>   !== Correct Answer - 3 ==   == Spark Answer - 0 ==
>>    struct<>                   struct<>
>>   ![1,10,2,null]
>>   ![2,10,4,null]
>>   ![3,10,6,null]
>>
>> - HDFSMetadataLog: metadata directory collision *** FAILED ***
>>   The await method on Waiter timed out. (HDFSMetadataLogSuite.scala:201)
>>
>> and then streaming suites that never finish
>>
>> On Thu, Jan 17, 2019 at 8:49 PM Takeshi Yamamuro <linguin....@gmail.com> 
>> wrote:
>> >
>> > Please vote on releasing the following candidate as Apache Spark version 
>> > 2.3.3.
>> >
>> > The vote is open until January 20 8:00PM (PST) and passes if a majority +1 
>> > PMC votes are cast, with
>> > a minimum of 3 +1 votes.
>> >
>> > [ ] +1 Release this package as Apache Spark 2.3.3
>> > [ ] -1 Do not release this package because ...
>> >
>> > To learn more about Apache Spark, please see http://spark.apache.org/
>> >
>> > The tag to be voted on is v2.3.3-rc1 (commit 
>> > b5ea9330e3072e99841270b10dc1d2248127064b):
>> > https://github.com/apache/spark/tree/v2.3.3-rc1
>> >
>> > The release files, including signatures, digests, etc. can be found at:
>> > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-bin/
>> >
>> > Signatures used for Spark RCs can be found in this file:
>> > https://dist.apache.org/repos/dist/dev/spark/KEYS
>> >
>> > The staging repository for this release can be found at:
>> > https://repository.apache.org/content/repositories/orgapachespark-1297
>> >
>> > The documentation corresponding to this release can be found at:
>> > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-docs/
>> >
>> > The list of bug fixes going into 2.3.3 can be found at the following URL:
>> > https://issues.apache.org/jira/projects/SPARK/versions/12343759
>> >
>> > FAQ
>> >
>> > =========================
>> > How can I help test this release?
>> > =========================
>> >
>> > If you are a Spark user, you can help us test this release by taking
>> > an existing Spark workload and running on this release candidate, then
>> > reporting any regressions.
>> >
>> > If you're working in PySpark you can set up a virtual env and install
>> > the current RC and see if anything important breaks, in the Java/Scala
>> > you can add the staging repository to your projects resolvers and test
>> > with the RC (make sure to clean up the artifact cache before/after so
>> > you don't end up building with a out of date RC going forward).
>> >
>> > ===========================================
>> > What should happen to JIRA tickets still targeting 2.3.3?
>> > ===========================================
>> >
>> > The current list of open tickets targeted at 2.3.3 can be found at:
>> > https://issues.apache.org/jira/projects/SPARK and search for "Target 
>> > Version/s" = 2.3.3
>> >
>> > Committers should look at those and triage. Extremely important bug
>> > fixes, documentation, and API tweaks that impact compatibility should
>> > be worked on immediately. Everything else please retarget to an
>> > appropriate release.
>> >
>> > ==================
>> > But my bug isn't fixed?
>> > ==================
>> >
>> > In order to make timely releases, we will typically not hold the
>> > release unless the bug in question is a regression from the previous
>> > release. That being said, if there is something which is a regression
>> > that has not been correctly targeted please ping me or a committer to
>> > help target the issue.
>> >
>> > --
>> > ---
>> > Takeshi Yamamuro
>
>
>
> --
> ---
> Takeshi Yamamuro

---------------------------------------------------------------------
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org

Reply via email to