Honestly I didn't even see this until now. I'll look into it folks, maybe
we could redirect the temp output to target if /tmp is not writable.
I'll defo have a look later

On Sep 26, 2016 6:06 PM, <[email protected]> wrote:

>
> dev Digest 27 Sep 2016 01:06:47 -0000 Issue 852
>
> Topics (messages 9169 through 9169)
>
> Re: [CassandraStore Tests] attempted to delete non-existing file...
>         9169 by: Renato Marroquín Mogrovejo
>
> Administrivia:
>
> ---------------------------------------------------------------------
> To post to the list, e-mail: [email protected]
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
> ----------------------------------------------------------------------
>
>
>
> ---------- Forwarded message ----------
> From: "Renato Marroquín Mogrovejo" <[email protected]>
> To: Gora Dev <[email protected]>
> Cc:
> Date: Mon, 26 Sep 2016 23:55:06 +0200
> Subject: Re: [CassandraStore Tests] attempted to delete non-existing
> file...
> Maybe Jenkins can't modify the path where Cassandra is writing to?
>
> http://stackoverflow.com/questions/26881066/how-to-
> solve-var-lib-cassandra-data-system-schema-columnfamilies-system-schema-c
>
> Lewis you are a Jenkins expert, any thoughts on this?
>
>
> Best,
>
> Renato M.
>
> 2016-09-22 23:20 GMT+02:00 Alfonso Nishikawa <[email protected]
> >:
>
> > Hi.
> >
> > Jenkis [1] fails because of this:
> >
> > "attempted to delete non-existing file
> > system-compaction_history-tmp-jb-533-Statistics.db"
> >
> > Anyone know how to fix it?
> > I know it does not means it is actually failing to build, but I guess it
> > will be good to have clean builds.
> >
> > Priority is "ultra low", just to know if someone has some intuition about
> > what is happening :)
> >
> > Regards,
> >
> > Alfonso
> >
> >
> > [1] -
> > https://builds.apache.org/job/gora-trunk/org.apache.gora$
> > gora-cassandra/1688/testReport/junit/org.apache.gora.cassandra.store/
> > TestCassandraStore/org_apache_gora_cassandra_store_TestCassandraStore/
> >
>
>

Reply via email to