Thanks Stephan, will send PR for it
On Friday, March 6, 2015, Stephan Ewen wrote:
> Ah, yeah, that is a vulnerability in the test. Same thing as in the other
> test. It gets created because you have root access and the test assumes it
> cannot be created.
>
> Safe thing to do is like in your oth
Ah, yeah, that is a vulnerability in the test. Same thing as in the other
test. It gets created because you have root access and the test assumes it
cannot be created.
Safe thing to do is like in your other fix: create a directory where the
user has no write permissions and set this to the BLOB st
Well, I need my morning coffee, just remember mvn will pull the right
version of akka appropriately.
The problem is that the BlobManager is started properly since my
machine somehow have "/does-not-exist-no-sir/" directory which is used
as target directory for the BlobSever which should fail.
The
Thanks Stephan, just noticed that line.
Seemed like there was issue in Akka 2.1.x where awaitTermination hang
when there is remote actors.
Need to check Akka version in my box.
- Henry
On Fri, Mar 6, 2015 at 1:11 AM, Stephan Ewen wrote:
> The failing test is the
> JobManagerStartupTest.testJob
The failing test is the
JobManagerStartupTest.testJobManagerStartupFails(JobManagerStartupTest.java:93)
Am 04.03.2015 21:47 schrieb "Henry Saputra (JIRA)" :
> Henry Saputra created FLINK-1651:
>
>
> Summary: Running mvn test got stuck
>
Thanks guys, will try it out.
On Thu, Mar 5, 2015 at 2:12 AM, Ufuk Celebi wrote:
> Thanks for reporting. Even if it runs on your Ubuntu box, it might still be
> a problem. It's actually nice to hear that it is reproducible.
>
> Can you do the following after it stalls:
>
> jps
>
> And then a jsta
Thanks for reporting. Even if it runs on your Ubuntu box, it might still be
a problem. It's actually nice to hear that it is reproducible.
Can you do the following after it stalls:
jps
And then a jstack for each process with a name like
"surefirebooter425130371299859".
Then we can see, whic
As I remember it was running test successfully last week. It is been a
while I ran full test in my env.
Will try to look more into it.
On Wed, Mar 4, 2015 at 11:44 PM, Till Rohrmann wrote:
> That is odd. I just ran mvn clean verify -Dmaven.javadoc.skip=true on my
> mac work machine and it ran th
That is odd. I just ran mvn clean verify -Dmaven.javadoc.skip=true on my
mac work machine and it ran through successfully.
Could you post which java processes are running when the console hangs? And
also the stack traces of all surefirebooter processes? Maybe someone can
make head or tail of it.
This is consistently repro in my mac work machine. Nothing really on
the JStack thread dump or Java Mission Control =(
The console just hang but do not see any deadlock from the thread trace.
- Henry
On Wed, Mar 4, 2015 at 11:02 PM, Till Rohrmann wrote:
> Is this reproducible? If so, then a sta
Is this reproducible? If so, then a stack trace of the JVM would be
helpful. With the stack trace we would know which test case stalls.
On Wed, Mar 4, 2015 at 9:46 PM, Henry Saputra (JIRA)
wrote:
> Henry Saputra created FLINK-1651:
>
>
> Summary:
Henry Saputra created FLINK-1651:
Summary: Running mvn test got stuck
Key: FLINK-1651
URL: https://issues.apache.org/jira/browse/FLINK-1651
Project: Flink
Issue Type: Bug
Components
12 matches
Mail list logo
