Enable tests on travis-ci

[dylanmckay]

Currently, most of our tests fail. this is because I wrote tests for every existing AVR instruction, including the ones that are not implemented. It is also because we have some encoding errors in several instructions.

Once we are in a passing state, get travis to run our tests in the build process.

[RandomInsano]

Travis should run any tests that would be checked by running 'make test' after the build succeeds.

How are the tests done? We can likely define our own build + test commands by adding something like this:

script:
  - ./configure
  - make
  - ./test-app

[dylanmckay]

Tests are executed using make check.

[dylanmckay]

I have got the AVR MC test suite to the point where there are only two issues left:

• MOVW Rd, Rr (Fix parsing of MOVW instruction #84)
• LDD/STD (Support parsing LDD/STD instructions #71)

I will mark them as XFAIL so that they are expected to fail. Our test suite should then pass, and we can fix the aforementioned tests and remove the XFAIL annotation.

[RandomInsano]

Noted! On my way home for dinner, will make the change tonight.

[dylanmckay]

Note that make check will attempt to run all tests (including x86,ARM,etc).

We pass -DLLVM_TARGETS_TO_BUILD="AVR" to CMake in .travis.yml, and so the tests will fail with make check (because "x86 is an unknown target").

We probably have to run the AVR tests manually. Because all AVR tests are parented by folders named AVR, it would be sufficient to call:

# run the LLVM testing tool (lit) on all files of type d (directory) with name "AVR"
llvm-lit $(find <llvm-root>/test -name AVR -type d)

[RandomInsano]

Yup, looks good over here. Even if make check failed due to missing targets, it makes sense to only test the AVR components.

I'll fold the tests in now and see how she goes.