Re: Wanted: Travis CI integration
Posted: Sat Apr 19, 2014 11:57 pm
Kinda related to both this discussion and https://github.com/micropython/micropython/issues/440 , rather than 'bloating' micropython with the run-time ability to detect what options it was compiled with, maybe a simpler option would be to just have the build-process spit out some kind of meta-file alongside the final uPy binary (whether that's unix, stmhal, windows, etc.) that specifies which options this particular binary was compiled with.
And then maybe there could be some additional meta-info contained inside each of the test-scripts (perhaps inside a comment-block), saying what 'features' the tests in that particular script rely on.
And then tying both these things together, run-tests could read in both sets of data, and then selectively choose which tests to run, based on what features are or aren't compiled into the particular micropython that is being tested; i.e. it would allow you to double-check that disabling one feature, wouldn't accidentally break another still-enabled feature.
Does that make sense, or would it be too much effort and be impractical? OTOH it would be a really good way of testing https://github.com/micropython/micropython/issues/35 if or when it ever gets implemented
Maybe I'm thinking too far ahead and going a bit over the top like I did in https://github.com/micropython/micropython/issues/495
And then maybe there could be some additional meta-info contained inside each of the test-scripts (perhaps inside a comment-block), saying what 'features' the tests in that particular script rely on.
And then tying both these things together, run-tests could read in both sets of data, and then selectively choose which tests to run, based on what features are or aren't compiled into the particular micropython that is being tested; i.e. it would allow you to double-check that disabling one feature, wouldn't accidentally break another still-enabled feature.
Does that make sense, or would it be too much effort and be impractical? OTOH it would be a really good way of testing https://github.com/micropython/micropython/issues/35 if or when it ever gets implemented
Maybe I'm thinking too far ahead and going a bit over the top like I did in https://github.com/micropython/micropython/issues/495