It is sufficient to check the scripted diffs on one arch, i.e. CHECK_DOC
==1.
Also, the default datadir should not be created by just running the tests.
It is sufficient to check the scripted diffs on one arch, i.e. CHECK_DOC
==1.
Also, the default datadir should not be created by just running the tests.
Concept ACK regarding the assertion
Is it due to performance reasons we want to run scripted diff only for the arm-linux-gnueabihf
build (CHECK_DOC=1
)? One benefit of doing the scripted diff for all builds is to make it apparent from the build status overview that all builds fails. If only arm-linux-gnueabihf
is red when a scripted diff fails it might look like a platform specific issue and hence require further investigation to see that it is a general scripted diff failure.
This argument could be raised for all checks that for performance reasons are specific to a given Travis build, but scripted diff should be fairly quick in the general case?
@MarcoFalke Makes sense! Factoring out CHECK_DOC
into a different build stage sounds like a good plan.
Concept ACK :-)