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
Thanks guys, will try it out.
On Thu, Mar 5, 2015 at 2:12 AM, Ufuk Celebi u...@apache.org 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
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, which
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
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 trohrm...@apache.org wrote:
That is odd. I just ran mvn clean verify -Dmaven.javadoc.skip=true on my
mac work
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.
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) j...@apache.org
wrote:
Henry Saputra created FLINK-1651:
