>>>>> On Fri, 04 Jun 2010 08:24:06 +0200, Magnus Fromreide >>>>> <[email protected]> said:
MF> The problem seems to be that I hadn't installed net-snmp prior to MF> running the test suite but I do believe that the test suite should be MF> runnable prior to net-snmp beeing installed. Yep; I hadn't gotten to doing paths yet. Note: the new full suite of tests is *not* designed to ensure every test is runnable by every person. This is a huge deviation from the previous testing platform. Only the *default* set of tests is expected to work for everyone in every environment. MF> On another host the tests also ended up in the summary report with the MF> same log (different perl version, same problem) but there I think the MF> problem is that the test was run in the first place since the following MF> part of configure-summary explains the situation: MF> Embedded Perl support: disabled MF> SNMP Perl modules: disabled Then you probably shouldn't be running the perl test group in the first place (or you should expect it to fail). [now, it should be checking for enabled perl and it should be doing include paths, but there will likely be some tests where this is impossible; for example the transport tests assume you have an IPv6 enabled interface and if you don't they will fail. We're not going to write a test to ensure that you have an ipv6 interface before running the test. In fact, one of the whole reasons the new test "groups" were created was specifically because of this one problem: we can't test for everything before testing] -- Wes Hardaker Please mail all replies to [email protected] ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
