Skip to content

Huge build logs make contributions impossible #1792

Closed as not planned
Closed as not planned

Description

@atsushieno

Here are what happens:

  • On Firefox, since the log page is too long, it cannot complete loading, gives up in the middle:

screenshot from 2018-06-08 05-56-32

  • On Chrome, it seems to load the complete log, but gives up rendering in the middle:

screenshot from 2018-06-08 06-04-40

screenshot from 2018-06-08 06-06-28

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.

Activity

  1. atsushieno commented on Jun 8, 2018

    @atsushieno
    ContributorAuthor

    These are the PRs / related issues, blocked by this issue: #1489 #1790 #1738

  2. atsushieno commented on Jun 14, 2018

    @atsushieno
    ContributorAuthor

    As commented on #1808 it cannot be closed only by that PR.

  3. jpobst commented on Aug 8, 2022

    @jpobst
    Contributor

    Jenkins is no longer used, so I think this issue is obsolete.

  4. ghost locked as resolved and limited conversation to collaborators on Sep 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions