From hfreyther at sysmocom.de Thu Apr 25 07:01:08 2013 From: hfreyther at sysmocom.de (Holger Hans Peter Freyther) Date: Thu, 25 Apr 2013 09:01:08 +0200 Subject: PCU VTY tests can not be enabled Message-ID: <20130425070108.GI20720@xiaoyu.lan> Dear Ivan, it appears to that starting from your configure.ac change the vty tests can not be eanbled anymore. E.g. compare this with the build results on the jenkins after your change. do you have time to fix that today? holger -- - Holger Freyther http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Schivelbeiner Str. 5 * 10439 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte From hfreyther at sysmocom.de Thu Apr 25 07:19:23 2013 From: hfreyther at sysmocom.de (Holger Hans Peter Freyther) Date: Thu, 25 Apr 2013 09:19:23 +0200 Subject: PCU VTY tests can not be enabled In-Reply-To: <20130425070108.GI20720@xiaoyu.lan> References: <20130425070108.GI20720@xiaoyu.lan> Message-ID: <20130425071923.GJ20720@xiaoyu.lan> On Thu, Apr 25, 2013 at 09:01:08AM +0200, Holger Hans Peter Freyther wrote: Dear Ivan, > it appears to that starting from your configure.ac change the vty tests > can not be eanbled anymore. E.g. compare this with the build results on > the jenkins after your change. four builds later I have them enabled again. The intention was to have tests ran when the osmo-python module is available but this has gone wrong. holger -- - Holger Freyther http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Schivelbeiner Str. 5 * 10439 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte From hfreyther at sysmocom.de Thu Apr 25 08:01:53 2013 From: hfreyther at sysmocom.de (Holger Hans Peter Freyther) Date: Thu, 25 Apr 2013 10:01:53 +0200 Subject: PCU VTY tests can not be enabled In-Reply-To: <20130425071923.GJ20720@xiaoyu.lan> References: <20130425070108.GI20720@xiaoyu.lan> <20130425071923.GJ20720@xiaoyu.lan> Message-ID: <20130425080153.GL20720@xiaoyu.lan> On Thu, Apr 25, 2013 at 09:19:23AM +0200, Holger Hans Peter Freyther wrote: > On Thu, Apr 25, 2013 at 09:01:08AM +0200, Holger Hans Peter Freyther wrote: > four builds later I have them enabled again. The intention was to have > tests ran when the osmo-python module is available but this has gone > wrong. argh.. now some tests fail... -- - Holger Freyther http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Schivelbeiner Str. 5 * 10439 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte From Ivan.Kluchnikov at fairwaves.ru Thu Apr 25 08:27:28 2013 From: Ivan.Kluchnikov at fairwaves.ru (Ivan Kluchnikov) Date: Thu, 25 Apr 2013 12:27:28 +0400 Subject: PCU VTY tests can not be enabled In-Reply-To: <20130425080153.GL20720@xiaoyu.lan> References: <20130425070108.GI20720@xiaoyu.lan> <20130425071923.GJ20720@xiaoyu.lan> <20130425080153.GL20720@xiaoyu.lan> Message-ID: Hi Holger, It is very strange. Build #151 is ok Triggering linux_i386_debian_squeeze,sysmobts=no,sysmodsp=no linux_i386_debian_squeeze,sysmobts=no,sysmodsp=no completed with result SUCCESS Triggering linux_i386_debian_squeeze,sysmobts=yes,sysmodsp=no linux_i386_debian_squeeze,sysmobts=yes,sysmodsp=no completed with result SUCCESS Triggering linux_i386_debian_squeeze,sysmobts=no,sysmodsp=yes linux_i386_debian_squeeze,sysmobts=no,sysmodsp=yes completed with result SUCCESS Triggering linux_i386_debian_squeeze,sysmobts=yes,sysmodsp=yes linux_i386_debian_squeeze,sysmobts=yes,sysmodsp=yes completed with result SUCCESS But build #152 is not ok Triggering linux_i386_debian_squeeze,sysmobts=no,sysmodsp=no linux_i386_debian_squeeze,sysmobts=no,sysmodsp=no completed with result SUCCESS Triggering linux_i386_debian_squeeze,sysmobts=yes,sysmodsp=no linux_i386_debian_squeeze,sysmobts=yes,sysmodsp=no completed with result FAILURE Triggering linux_i386_debian_squeeze,sysmobts=no,sysmodsp=yes linux_i386_debian_squeeze,sysmobts=no,sysmodsp=yes completed with result SUCCESS Triggering linux_i386_debian_squeeze,sysmobts=yes,sysmodsp=yes linux_i386_debian_squeeze,sysmobts=yes,sysmodsp=yes completed with result FAILURE But I see FAILURE only when sysmobts=yes. 2013/4/25 Holger Hans Peter Freyther > On Thu, Apr 25, 2013 at 09:19:23AM +0200, Holger Hans Peter Freyther wrote: > > On Thu, Apr 25, 2013 at 09:01:08AM +0200, Holger Hans Peter Freyther > wrote: > > > four builds later I have them enabled again. The intention was to have > > tests ran when the osmo-python module is available but this has gone > > wrong. > > argh.. now some tests fail... > > -- > - Holger Freyther http://www.sysmocom.de/ > ======================================================================= > * sysmocom - systems for mobile communications GmbH > * Schivelbeiner Str. 5 > * 10439 Berlin, Germany > * Sitz / Registered office: Berlin, HRB 134158 B > * Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte > > > -- Regards, Ivan Kluchnikov. http://fairwaves.ru -------------- next part -------------- An HTML attachment was scrubbed... URL: