summaryrefslogtreecommitdiff
path: root/tests/lmp-v.tests
diff options
context:
space:
mode:
authorGuy Harris <guy@alum.mit.edu>2020-02-04 15:47:02 -0800
committerGuy Harris <guy@alum.mit.edu>2020-02-04 15:47:02 -0800
commit895e3dfd766bd2858e1514ec21554c22de587149 (patch)
tree7a817e90142a022d6829b5fc669efe8cf1a64e29 /tests/lmp-v.tests
parentfa7028248974c27a5089988198e8171b4a061d56 (diff)
downloadtcpdump-895e3dfd766bd2858e1514ec21554c22de587149.tar.gz
Remove the hacks to avoid floating-point issues in the tcpdump checks.
I can't seem to make those issues pop up on my (x86-64) machine, and, if they do show up on any platforms, the best hack to handle it is probably to have a special tcpdump flag to force it to do a floating-point calculation and see what result is generated, and report the result, so we know what it'll do with the numbers in the test files, and have tests/TESTrun run tcpdump with that flag. If those tests *do* fail, we'll know what calculations to do.
Diffstat (limited to 'tests/lmp-v.tests')
-rw-r--r--tests/lmp-v.tests1
1 files changed, 0 insertions, 1 deletions
diff --git a/tests/lmp-v.tests b/tests/lmp-v.tests
index 27232512..01c4ede1 100644
--- a/tests/lmp-v.tests
+++ b/tests/lmp-v.tests
@@ -8,7 +8,6 @@
$testlist = [
{
- config_set => 'USING_GCC',
name => 'lmp-v',
input => 'lmp.pcap',
output => 'lmp-v.out',