[
https://issues.apache.org/jira/browse/NIFI-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858559#comment-16858559
]
David Sargrad commented on NIFI-6343:
-------------------------------------
I really have a lot of problems building the NIFI system. I have run many build
attempts, and each and every time it seems to fail in a different way, often on
seemingly random packages. I've started to avoid building the unit tests, since
they too are problematic. I have successfully built the whole system once or
twice. I've attempted to build the whole system (on exactly the same code
base), about 20 times.
I've been trying to build as follows (per getting started documentation--- with
the addition of the skip):
mvn -T C2.0 install -Dmaven.test.skip=true
> nifi-ignite-processors fails to build because /tmp/ignite was owned by another
> ------------------------------------------------------------------------------
>
> Key: NIFI-6343
> URL: https://issues.apache.org/jira/browse/NIFI-6343
> Project: Apache NiFi
> Issue Type: Bug
> Environment: centos 7
> java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64
> Reporter: David Sargrad
> Priority: Major
> Attachments: image-2019-06-03-11-57-12-907.png,
> image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png,
> image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png,
> image-2019-06-03-12-04-06-699.png, image-2019-06-03-12-47-07-720.png
>
>
> The nifi build fails again and again on nifi-ignite-processors. It seems to
> build everything else successfully.
>
>
> !image-2019-06-03-12-04-06-699.png!
>
>
>
> It turns out that the test case attempts to write to /tmp/ignite.
>
> !image-2019-06-03-12-02-59-709.png!
>
>
>
> However if another user on the same computer ran a past build of nifi, then
> that /tmp/ignite directory is not writable (nor is it cleaned up). It would
> seem that such test cases should not write in a /tmp directory that is shared.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)