I just changed the code so that if you set the environment variable
BROKENDNS it will ignore this error.
It will push upstream when the test sequence completes - usually about
10-12 minutes from now.
On 11/14/2013 06:35 AM, Alan Robertson wrote:
This seems to be the problem...
+ testify
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
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
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
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
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
Wrong Jim Williams. Good luck with twitter. If you bought stock, I hope you
did so early in the morning yesterday rather than afternoon.
On Friday, November 8, 2013, John Carpenter wrote:
aw man! i guess it was user error after all.. i mustve missed those tweets
(like this one):
