Bluepill reporting issue

[ravimandala]

Bluepill logs fail to parse xml test reports and throws errors like...

{6971} 20220112.005927 [  INFO  ] (BLUEPILL) All BPs have finished.
{6971} 20220112.005927 [  INFO  ] (BLUEPILL) Trace profile: /<redacted>/bin/VoyagerScenarioTests9_xcscheme.sh.runfiles/__main__/bp_exec_root/outputs/trace-profile.json
{6971} 20220112.005932 [  ERROR ] (BLUEPILL) Failed to parse '/<redacted>/bin/VoyagerScenarioTests9_xcscheme.sh.runfiles/__main__/bp_exec_root/outputs/BP-8/TEST-VoyagerParticipateUnitTests-2-results.xml': line 1 column 1 - Warning: discarding unexpected plain text
1 warning, 0 errors were found!

{6971} 20220112.005932 [  ERROR ] (BLUEPILL) SOME TESTS MIGHT BE MISSING
{6971} 20220112.005932 [  ERROR ] (BLUEPILL) Failed to parse '/<redacted>/bin/VoyagerScenarioTests9_xcscheme.sh.runfiles/__main__/bp_exec_root/outputs/BP-8/TEST-VoyagerParticipateUnitTests-3-results.xml': line 1 column 1 - Warning: discarding unexpected plain text
1 warning, 0 errors were found!

{6971} 20220112.005932 [  ERROR ] (BLUEPILL) SOME TESTS MIGHT BE MISSING
{6971} 20220112.005932 [  ERROR ] (BLUEPILL) Failed to parse '/<redacted>/bin/VoyagerScenarioTests9_xcscheme.sh.runfiles/__main__/bp_exec_root/outputs/BP-8/TEST-VoyagerParticipateUnitTests-4-results.xml': line 1 column 1 - Warning: discarding unexpected plain text
1 warning, 0 errors were found!

{6971} 20220112.005932 [  ERROR ] (BLUEPILL) SOME TESTS MIGHT BE MISSING
{6971} 20220112.005933 [  INFO  ] (BLUEPILL) HTML report: /<redacted>/bin/VoyagerScenarioTests9_xcscheme.sh.runfiles/__main__/bp_exec_root/outputs/0-test-report.html

In the above example, while TEST-VoyagerParticipateUnitTests-3-results.xml and TEST-VoyagerParticipateUnitTests-4-results.xml were valid xml files, the file TEST-VoyagerParticipateUnitTests-2-results.xml has the below text which I believe is causing the issue.

NO LOG: JUnitReporter

Please take a look.
\cc @ob @chenxiao0228

[ravimandala]

This issue might be a duplicate of the issue-#517. Will test it with a release after the fix PR-#515 and resolve both these issues.

[ravimandala]

While PR#515 might have fixed Issue#517, the reason why some reports have the below text might still needs to be fixed.

NO LOG: JUnitReporter