When we update Chromium / Phantom, reporting does not always update its binaries. The reason is that reporting simply checks to make sure there is a binary where it expects. It doesn't check that the binary is the actual binary it's expecting. The fix is to have reporting check the md5 hash of existing binaries, and overwrite the binaries if the md5 does not meet expectations.
When we update Chromium / Phantom, reporting does not always update its binaries. The reason is that reporting simply checks to make sure there is a binary where it expects. It doesn't check that the binary is the actual binary it's expecting. The fix is to have reporting check the md5 hash of existing binaries, and overwrite the binaries if the md5 does not meet expectations.