Successful test run but logs are MIA

testRunStarted EMULATOR30X0X5X0
testStarted EMULATOR30X0X5X0 test = TestIdentifier(className=component_ui_tests.ChallengeSelectionUiTest, testName=noMethodsAvailableTest)
88% | [omni]-[EMULATOR30X0X5X0] component_ui_tests.ChallengeSelectionUiTest#noMethodsAvailableTest started
join 1003ms
Removed file in 786ms /sdcard/component_ui_tests.ChallengeSelectionUiTest-noMethodsAvailableTest.mp4
testEnded EMULATOR30X0X5X0 test = TestIdentifier(className=component_ui_tests.ChallengeSelectionUiTest, testName=noMethodsAvailableTest)
100% | [omni]-[EMULATOR30X0X5X0] component_ui_tests.ChallengeSelectionUiTest#noMethodsAvailableTest ended
testRunEnded elapsedTime 3679

> Task :challenge:challenge-implementation:marathonDebugAndroidTest
handle test results EMULATOR30X0X5X0
request next batch for device EMULATOR30X0X5X0
terminate EMULATOR30X0X5X0

Recording finished in 4984ms /sdcard/component_ui_tests.ChallengeSelectionUiTest-noMethodsAvailableTest.mp4
Recording finished in 24284ms /sdcard/component_ui_tests.ChallengeSelectionUiTest-phoneStableUnstable_1.mp4
Recording finished in 31160ms /sdcard/component_ui_tests.ChallengeSelectionUiTest-phoneStableUnstable_2.mp4
Recording finished in 40965ms /sdcard/component_ui_tests.ChallengeSelectionUiTest-phoneStableUnstable_4.mp4
Recording finished in 17526ms /sdcard/component_ui_tests.ChallengeSelectionUiTest-otpEmailInAndOut.mp4
Recording finished in 45761ms /sdcard/component_ui_tests.ChallengeSelectionUiTest-phoneStableUnstable_5.mp4
Recording finished in 36341ms /sdcard/component_ui_tests.ChallengeSelectionUiTest-phoneStableUnstable_3.mp4
Recording finished in 55646ms /sdcard/component_ui_tests.ChallengeSelectionUiTest-enterChallengeMethodsAndCancelTest.mp4

> Task :challenge:challenge-implementation:marathonDebugAndroidTest
Allure environment data saved.
Marathon run finished:
Device pool omni:
        8 passed, 0 failed, 0 ignored tests
        Flakiness overhead: 0ms
        Raw: 8 passed, 0 failed, 0 ignored, 0 incomplete tests
Total time: 0H 1m 0s


Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.3/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 1m 9s
832 actionable tasks: 1 executed, 831 up-to-date

However, logs for the test never load.

[Malinskiy]

Which version of marathon are you using? Do the log files have content?

With the video - this is a known issue with some devices: the screenrecorder binary might not work properly on them. You can double check if it works by running adb shell screenrecorder. Marathon detects only the presence of this binary and assumes that it’s working.

[Malinskiy]

@ZakTaccardi this is not a limitation of marathon, but a limitation of browsers that care about your security and block suspicious cross-site requests .

For a CI use-case, there is no such issue since all of them share the report via some form of HTTP server. For a local development use-case: most people use an IDE and have the HTTP server there. Just right click on the report HTML and open in your browser of choice. If you’re a vim/emacs adept then you should be able to start a docker run with nginx without any issue.

The only way to overcome this in marathon is to embed the content directly into the HTML which I don’t think should be done: this will increase the size almost twice for the report directory. These video/screenshot/log files are shared between multiple reports that we generate and duplicating them would not be feasible.