Yup I ran it again with 1.6.0 version of py2neo but don't think that fixed the errors. I write more in detail tomorrow. You can see logs in the usual spot.
-- JC > On Nov 13, 2013, at 2:04 PM, Alan Robertson <al...@unix.sh> wrote: > > JC: > > Have you had a chance to make this change yet? > > Have questions? > > >> On 11/10/2013 08:28 AM, Alan Robertson wrote: >> Hi, >> >> When I rewrote the database code I switched to requiring the latest version >> of Py2neo. This is a required change. I think this is version 1.6.0. But >> it will NOT work with 1.5.x. >> >> It should run with the latest stable Neo4j, but I've been testing with the >> 2.0.x test version. >> >> I aim to have this run with the 2.x version of Neo4j when it becomes >> official. >> >> The problems now in the logs look like they're related to py2neo version. >> >> >>> On 11/8/2013 1:26 PM, John Carpenter wrote: >>> aw man! i guess it was user error after all.. i mustve missed those tweets >>> (like this one): >>> >>> https://twitter.com/AllegNotifier/status/398615383633956864 >>> >>> so good news... notifier still works. bad news still failing tests. also i >>> should fix the logic in my script so that when it passes, it'll still send >>> tweet. >>> >>> latest build console output are found here: >>> http://www.spathiwa.com/jenkins/builds.html >>> >>> im running it again right now (in case new changes got added) >>> >>> -- JC >>> >>> >>> >>> >>>> On Fri, Nov 8, 2013 at 10:19 AM, Alan Robertson <al...@unix.sh> wrote: >>>> Sounds great! >>>> >>>> Fwiffo <borgif...@gmail.com> wrote: >>>>> >>>>> I ran a set of builds right after you said you had made changes and I was >>>>> waiting for my twitter notification to pop up but it never did. Just now >>>>> I realized that the way I scripted it was to send notification on build >>>>> failure so the fact that I got no notice is surely a good sign! I'm eager >>>>> to verify the status of the builds (and to fix my script logic). >>>>> >>>>> >>>>> -- JC >>>>> >>>>>> On Nov 8, 2013, at 5:00 AM, Alan Robertson <al...@unix.sh> wrote: >>>>>> >>>>>> >>>>>> Hi, >>>>>> >>>>>> As was noted earlier on the list, the code didn't pass tests. Yesterday >>>>>> I got it to pass tests (didn't install something correctly), and late >>>>>> last night, I fixed some bugs that kept it from running correctly. >>>>>> >>>>>> >>>>>> Next week after I'm home, I'll work a bit more in earnest to ensure that >>>>>> it is a bit better tested. >>>>>> >>>>>> The current unit tes >>>>>> ts are >>>>>> nice, but they are only unit tests. >>>>>> >>>>>> Anyone who wants to volunteer to look at higher level system testing - >>>>>> please send an email to the list. >>>>>> >>>>>> Thanks! >>>>>> >>>>>> -- Alan Robertson >>>>>> al...@unix.sh >>>>>> >>>>>> >>>>>> Assimilation mailing list - Discovery-Driven Monitoring >>>>>> Assimilation@lists.community.tummy.com >>>>>> http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation >>>>>> >>>>>> http://assimmon.org/ >>>> >>>> -- >>>> Sent from my Android phone with K-9 Mail. Please excuse my brevity. >> >> >> >> _______________________________________________ >> Assimilation mailing list - Discovery-Driven Monitoring >> Assimilation@lists.community.tummy.com >> http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation >> http://assimmon.org/ > > > -- > Alan Robertson <al...@unix.sh> - @OSSAlanR > > "Openness is the foundation and preservative of friendship... Let me claim > from you at all times your undisguised opinions." - William Wilberforce
_______________________________________________ Assimilation mailing list - Discovery-Driven Monitoring Assimilation@lists.community.tummy.com http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation http://assimmon.org/
