OK. These are the test classes that fail for me when building on Windows (in rya.shell and rya.streams.integration). We could potentially add some JUnit assumptions to temporarily ignore these classes on Windows until a better solution is in place. That way it would build and we could mark those projects as known issues on Windows.
extras/rya.streams/integration/src/test/java/org/apache/rya/streams/kafka/processors/aggregation/AggregationProcessorIT.java extras/rya.streams/integration/src/test/java/org/apache/rya/streams/kafka/processors/join/JoinProcessorIT.java extras/rya.streams/integration/src/test/java/org/apache/rya/streams/kafka/processors/projection/MultiProjectionProcessorIT.java extras/rya.streams/integration/src/test/java/org/apache/rya/streams/kafka/processors/sp/StatementPatternProcessorIT.java extras/shell/src/test/java/org/apache/rya/shell/AccumuloRyaConnectionCommandsIT.java extras/shell/src/test/java/org/apache/rya/shell/MongoRyaShellIT.java -----Original Message----- From: White, Eric [mailto:eric.wh...@parsons.com] Sent: Friday, February 16, 2018 1:39 PM To: dev@rya.incubator.apache.org Subject: RE: Release build fails on Windows I ignored the 2 test files giving that problem but ran into another build issue on 64-bit Windows with Kafka. It seems there's a problem with Kafka 0.10.0.1 not correctly bundling RocksDB in the jar (Error message: "librocksdbjni-win64.dll was not found inside JAR"). There's a Kafka JIRA ticket for this: https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_KAFKA-2D4316&d=DwIGaQ&c=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10&r=RaJkRMooYbg4vmML14E10F9hYEBLOeOHS3mAimFNgqQ&m=Suwk7RNCtXna4YgKFMJfmITYVnJzd_AXAck_edQw-zg&s=HaonPQAcgBYosCJokbdZNJ6bJdBdNkD8huSWgsKFUYo&e= This is supposed to be resolved in Kafka 0.10.1 (already released). I'll see if ignoring those failing tests will make the Rya build pass on Windows. -----Original Message----- From: Puja Valiyil [mailto:puja...@gmail.com] Sent: Thursday, February 15, 2018 1:42 PM To: dev@rya.incubator.apache.org Subject: Re: Release build fails on Windows Ok, I would vote to mark it as a known issue then. Is there any concern if the release doesn't build under windows? I don't see that being an issue personally. On Thu, Feb 15, 2018 at 1:32 PM, White, Eric <eric.wh...@parsons.com> wrote: > I can try but that probably won't fix it since it determines that the > owner of “user.home” is system and that’s not the same as administrator. > > -----Original Message----- > From: Puja Valiyil [mailto:puja...@gmail.com] > Sent: Thursday, February 15, 2018 1:24 PM > To: dev@rya.incubator.apache.org > Subject: Re: Release build fails on Windows > > Did you try running as an administrator? > I think that we should probably mark this as a known issue -- I don't > feel it should hold up the release. There have been lots of issues > with people building on windows, this is part of a larger issue I feel. > > On Thu, Feb 15, 2018 at 1:11 PM, White, Eric <eric.wh...@parsons.com> > wrote: > > > I ran into issues building the release (3.2.12-rc1) on a Windows > > machine with git bash. It seems some of the new Rya Shell tests > > fail due to the new PathUtils class (from another commit) saying > > "Operation of a file in a shared directory is not allowed" when > > attempting to add the .rya_shell_history file to "user.home". > > > > It seems it expects "user.home" to be owned by the user or an > > administrator, but it's owned by the system and fails. > > > > Thanks, > > -Eric White > > >
