3 Mar
2016
3 Mar
'16
6:17 p.m.
Yes, the test failure is due to additional logging introduced in
22d7e75e1f160e5337140d9f3dcb2679b621b646.
I was planning to fix it alongside with additional feedback I've got for
this commit but it got postponed due to other tasks.
On 03/03/2016 02:04 PM, Holger Freyther wrote:
--
Max Suraev <msuraev(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte
On 03 Mar
2016, at 13:31, Saurabh Sharan <Saurabh.Sharan(a)radisys.com> wrote:
Hello All,
Hi!
In the latest master, Unit test for TBF is
failing. Please find the attached tests/testsuite.log with this mail.
I was working on resubmission of padding encoding patch wherein this failure was noticed.
yes, I had hoped for Max to notice and fix it. The Coverity tool has noticed a
copy-and-paste error and I assume he needs to update the expected test result. I will have
a look at it tonight.
holger