run adb command after Espresso test (feature request ?)

First of all, thank you for the action.

For example

  - name: Android Emulator test
    uses: ReactiveCircus/android-emulator-runner@v2.8.0
    with:
      api-level: 28
      disable-animations: true
      arch: x86_64
      profile: Nexus 6
      script: ./gradlew cAT

Sometimes a process crashes

Starting 0 tests on test(AVD) - 9 Tests on test(AVD) - 9 failed: Instrumentation run failed due to ‘Process crashed.’

and I want to upload output of adb logcat , especial on a crash.

Does someone has a clue, how to do this ? Or is this a simple feature request to run a custom command after action ?

Thank you

[hannesa2]

Just for the records, this is the final way I go without color noise

      script: |
        adb logcat -c
        adb logcat *:E &
        ./gradlew cAT

Thank you !

[ychescale9]

I’m going to close this issue now. Please feel free to re-open or create another one if you run into other issues 😃