-
Notifications
You must be signed in to change notification settings - Fork 566
Closed as not planned
Labels
Area: xamarin-android BuildIssues building the xamarin-android repo *itself*.Issues building the xamarin-android repo *itself*.
Description
- Open a Jenkins build result page e.g. https://jenkins.mono-project.com/job/xamarin-anroid-linux-pr-builder/2993/
- Click "Indication 1"
Here are what happens:
- On Firefox, since the log page is too long, it cannot complete loading, gives up in the middle:
- On Chrome, it seems to load the complete log, but gives up rendering in the middle:
Whether it is a Chrome issue or not does not matter. What is important here is that Xamarin does not give sane way to diagnose any blocking problem for contributors (and of course our own) pull requests.
We have to fix this either 1) by reducing insane amount of build logs, or 2) provide any way to diagnose logs.
Actually 2) is not really a viable solution. Xamarin cannot ask contributors to read hundreds of megabytes of single build logs to investigate.
When we were using old CI server (wrench) it had never occurred because each build steps were split and we had to read only relevant log parts.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Area: xamarin-android BuildIssues building the xamarin-android repo *itself*.Issues building the xamarin-android repo *itself*.


