[asterisk-bugs] [DAHDI-tools 0018573]: dahdi_test accurately reports nonsense

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Jan 4 20:23:32 UTC 2011


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18573 
====================================================================== 
Reported By:                smurfix
Assigned To:                
====================================================================== 
Project:                    DAHDI-tools
Issue ID:                   18573
Category:                   Utilities
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
JIRA:                        
Reviewboard Link:            
====================================================================== 
Date Submitted:             2011-01-04 06:22 CST
Last Modified:              2011-01-04 14:23 CST
====================================================================== 
Summary:                    dahdi_test accurately reports nonsense
Description: 
dahdi_test reports -200% or 400% accuracy.

That's clearly stupid.

Also, the percentage printed in verbose mode clearly doesn't match the one
printed in terse mode.

SVN trunk as of last week.
====================================================================== 

---------------------------------------------------------------------- 
 (0130157) smurfix (reporter) - 2011-01-04 14:23
 https://issues.asterisk.org/view.php?id=18573#c130157 
---------------------------------------------------------------------- 
# dahdi_test -v& sleep 6; killall dahdi_test

Hmm, isn't that what "dahdi_test -c5" is supposed to do? ;-)

Anyway:

root at lab:~# dahdi_scan 
[1]
active=yes
alarms=UNCONFIGURED
description=DAHDI_DUMMY/1 (source: HRtimer) 1
name=DAHDI_DUMMY/1
manufacturer=
devicetype=DAHDI Dummy Timing
location=
basechan=1
totchans=0
irq=0
root at lab:~# 

So it seems that a broken patch in my build script mistakenly enabled
dahdi_dummy, and that dahdi_dummy is currently not only out-of-date but
broken. My bad.

root at lab:~# rmmod dahdi_dummy
root at lab:~# dahdi_test -v -c5
Opened pseudo dahdi interface, measuring accuracy...

8192 samples in 8191.384 system clock sample intervals (99.992%)
8192 samples in 8190.648 system clock sample intervals (99.983%)
8192 samples in 8191.256 system clock sample intervals (99.991%)
8192 samples in 8191.128 system clock sample intervals (99.989%)
8192 samples in 8191.136 system clock sample intervals (99.989%)
--- Results after 5 passes ---
Best: 99.992 -- Worst: 99.983 -- Average: 99.989207, Difference:
99.989208

OK, so now please fix the "Difference:" part of the result. :-P 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-01-04 14:23 smurfix        Note Added: 0130157                          
======================================================================




More information about the asterisk-bugs mailing list