You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 5, 2019. It is now read-only.
If JUnit test results exist--for example, as generated by a tool like ci_reporter--we should recognize them and use them to render completion rates and build failures. Running the entire build log through BuildLogParser on every render of the build page isn't efficient and requires a great deal of ongoing maintenance.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If JUnit test results exist--for example, as generated by a tool like ci_reporter--we should recognize them and use them to render completion rates and build failures. Running the entire build log through BuildLogParser on every render of the build page isn't efficient and requires a great deal of ongoing maintenance.
The text was updated successfully, but these errors were encountered: