add scenarios to CI

.github/workflows/test_challenge_fault.yml

+name: Test Challenge Fault
+
+on: [push, pull_request]
+
+jobs:
+  unit:
+    name: Fault injection challenge scenario
+    runs-on: ubuntu-latest
+    steps:
+    - name: Checkout Code
+      uses: actions/checkout@v2
+    - name: Install Toolchain (Go, Node.js, Yarn and Make)
+      run: |
+        sudo apt-get update
+        sudo apt-get -y --no-install-recommends install golang-1.16 nodejs npm make
+        npm install --global yarn
+    - name: Build
+      run: make build
+    - name: Run fault injection challenge scenario
+      run: demo/challenge_fault.sh

.github/workflows/test_challenge_simple.yml

+name: Test Challenge Simple
+
+on: [push, pull_request]
+
+jobs:
+  unit:
+    name: Simple challenge scenario
+    runs-on: ubuntu-latest
+    steps:
+    - name: Checkout Code
+      uses: actions/checkout@v2
+    - name: Install Toolchain (Go, Node.js, Yarn and Make)
+      run: |
+        sudo apt-get update
+        sudo apt-get -y --no-install-recommends install golang-1.16 nodejs npm make
+        npm install --global yarn
+    - name: Build
+      run: make build
+    - name: Run simple challenge scenario
+      run: demo/challenge_simple.sh

README.md

@@ -37,6 +37,8 @@ contracts -- A Merkleized MIPS processor on chain + the challenge logic
 
 ## Building
 
+Pre-requisites: Go, Node.js, Yarn (`npm install -g yarn`) and Make.
+
 ```
 make build
 make test # verify everything works correctly

build_unicorn.sh

@@ -8,3 +8,9 @@ cd unicorn2
 cmake . -DUNICORN_ARCH=mips -DCMAKE_BUILD_TYPE=Release
 #cmake . -DUNICORN_ARCH=mips -DCMAKE_BUILD_TYPE=Debug
 make -j8
+
+# export LIBUNICORN_PATH for Github CI
+# TODO: is this actually needed?
+if [[ ! -z "$GITHUB_ENV" ]]; then
+    echo "LIBUNICORN_PATH=$(pwd)/unicorn2/" >> $GITHUB_ENV
+fi