Comment 1 for bug 1857129

This bug is caused by invalid lshw output, and I don't see any obvious workaround short of a serious re-write of the memory/info test. Others are working on the lshw bug; with any luck a fix will be available before Ubuntu 20.04 is released. If not, we may need to drop or seriously re-work the memory/info test; but with progress being made on the underlying bug, it seems best to wait a bit before committing resources to a workaround. See also bug #1840462, which closely parallels this one.