Hi JC, I finally got around to looking at your outputs (stuck at a hotel in Oklahoma).
Here's one problem I know the exact solution to: ** (process:19306): WARNING **: resourceocf_new.97: No OCF Resource agent [/usr/lib/ocf/resource.d/heartbeat/Dummy] This is because you need the basic set of OCF resource agents installed for this test to work. Sorry I forgot to mention that. Although the code doesn't yet _do_ any monitoring, it has the tests to make sure the monitoring code we have works properly. To do that, it needs a resource agent. The Dummy resource agent is a harmless do-nothing agent that works great for testing -- so I used it... Not sure if this ran before or after I lowered the level of valgrind pickiness (but I don't think so). If you could add that dependency and reextract from tip and try again, that would be awesome!! I apologize for ignoring this for a long time - it's a HUGE amount of work to get all this going. Much appreciated! On 09/19/2013 06:57 PM, John Carpenter wrote: > ah i finished the twitter notification thingy a little early... was > too excited to just let it sit till weekend. check it out here: > https://twitter.com/allegnotifier > > i just repurposed one of my old twitter accounts that i used for > notifying other stuff. of course i can pick a different twitter > account if you want or put in some hashtags, etc. > > the beauty of this system is that an opt-in solution (ie. if u follow > @allegnotifier) > > i still got extra work to do.. like detecting if the build succeeded > or failed (right now im just notifying and outputting to gists on > failures since the tests always fail :P) > > -- JC > > > On Thu, Sep 19, 2013 at 10:56 AM, John Carpenter <[email protected] > <mailto:[email protected]>> wrote: > > yup.. now if i could just make those tests pass successfully > > i can also add in something like twitter notification too (worked > w/ the api in the past).. seems like it would make sense to alert > folks that a particular build finished > > ill find some time in weekend to do this > > -- JC > > > On Thu, Sep 19, 2013 at 5:35 AM, Alan Robertson <[email protected] > <mailto:[email protected]>> wrote: > > This sounds awesome! > > I have been busy trying to get all my code working, so I > haven't had a chance to look at it, but it DOES sound wonderful! > > -- Alan Robertson > [email protected] <mailto:[email protected]> > > > > > On 9/15/2013 10:35 PM, John Carpenter wrote: >> One challenge I've had with continuous integration behind my >> firewall is that I couldn't publish the results so that >> others would know whether builds/tests were successful. I've >> bridged this gap by writing a small post-build script that >> takes the build logs and posts them at gists.github.com >> <http://gists.github.com> (available for viewing publicly w/o >> login) after a build is finished. >> >> Here you can inspect the build >> logs: http://www.spathiwa.com/jenkins/builds.html >> >> These gists are automatically updated every time I run a >> build (thanks to post-build script). I'll continue to improve >> on the format and the amount of information shown. I plan to >> display whether the build was successful and also make the >> build number more apparent. >> >> When you click the link, you will see 6 hostnames, each >> corresponding to a particular version of Ubuntu and >> architecture. Clicking on the hostname itself will take you >> to the console output of the build. >> >> Please take a look and let me know suggestions / improvements. >> >> -- JC >> >> >> _______________________________________________ >> Assimilation mailing list - Discovery-Driven Monitoring >> [email protected] >> <mailto:[email protected]> >> >> http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation >> http://assimmon.org/ > > >
_______________________________________________ Assimilation mailing list - Discovery-Driven Monitoring [email protected] http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation http://assimmon.org/
