Disable broken bmpblock_utility test
The current bmpblock_utility doesn't preserve the order of images as
specified in the config yaml file. This doesn't affect the
functioning of the firmware, but does break this overly-restrictive
test.
Filed crosbug.com/19541 to fix this after Bill's current refactoring.
BUG=chromium-os:19541
TEST=make && make runtests
Change-Id: I03fe817bd191fec5f65aad37561a3224b6a2b1e6
Reviewed-on: http://gerrit.chromium.org/gerrit/6512
Reviewed-by: Bill Richardson <wfrichar@chromium.org>
Tested-by: Randall Spangler <rspangler@chromium.org>
diff --git a/tests/bitmaps/TestBmpBlock.py b/tests/bitmaps/TestBmpBlock.py
index ca7ef4a..8f47fe4 100755
--- a/tests/bitmaps/TestBmpBlock.py
+++ b/tests/bitmaps/TestBmpBlock.py
@@ -154,8 +154,12 @@
rc, out, err = runprog('/bin/rm', '-f', 'ORDER1', 'ORDER2')
self.assertEqual(0, rc)
- def testReproduce(self):
+ def disabledTestReproduce(self):
"""Equivalent yaml files should produce identical bmpblocks"""
+ # TODO: This test is currently broken because bmpblock_utility
+ # uses a map to hold the images, and the map doesn't preserve image
+ # order. So a simple compare is insufficient to determine that
+ # the bmpblocks are equivalent. See crosbug.com/19541.
rc, out, err = runprog(prog, '-c', 'case_order1.yaml', 'ORDER1')
self.assertEqual(0, rc)
rc, out, err = runprog(prog, '-c', 'case_order2.yaml', 'ORDER2')
@@ -201,4 +205,3 @@
prog = os.environ[varname]
print "Testing prog...", prog
unittest.main()
-