[CI] Generate full baseline upon PHPStan failure

Created on 31 October 2024, 4 months ago

Problem/Motivation

When a PHPStan job fails for core, a new baseline file artifact is generated. However, that is an incremental one (i.e. contains entries only for the NEW failures).

It would be more helpful to get a full baseline file so to copypaste it in the mr branch as is.

See https://drupal.slack.com/archives/CGKLP028K/p1730242123771039 for some insights.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Feature request
Status

Active

Version

11.0 🔥

Component

base system

Created by

🇮🇹Italy mondrake 🇮🇹

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @mondrake
  • 🇮🇹Italy mondrake 🇮🇹
  • Merge request !10903Closes #3484896 → (Open) created by mondrake
  • Pipeline finished with Failed
    about 1 month ago
    Total: 89s
    #395620
  • Pipeline finished with Failed
    about 1 month ago
    Total: 147s
    #395630
  • Pipeline finished with Failed
    about 1 month ago
    Total: 148s
    #395676
  • Pipeline finished with Failed
    about 1 month ago
    Total: 98s
    #395693
  • Pipeline finished with Failed
    about 1 month ago
    Total: 82s
    #395706
  • Pipeline finished with Failed
    about 1 month ago
    Total: 139s
    #395718
  • Pipeline finished with Failed
    about 1 month ago
    Total: 101s
    #395758
  • Pipeline finished with Failed
    about 1 month ago
    Total: 86s
    #395763
  • Pipeline finished with Failed
    about 1 month ago
    Total: 88s
    #395770
  • Pipeline finished with Success
    about 1 month ago
    Total: 459s
    #395774
  • Pipeline finished with Failed
    about 1 month ago
    Total: 104s
    #395877
  • Pipeline finished with Failed
    about 1 month ago
    Total: 95s
    #395881
  • Pipeline finished with Failed
    about 1 month ago
    Total: 179s
    #395884
  • Pipeline finished with Failed
    about 1 month ago
    Total: 108s
    #395888
  • Pipeline finished with Failed
    about 1 month ago
    Total: 90s
    #395897
  • Pipeline finished with Failed
    about 1 month ago
    Total: 99s
    #395905
  • Pipeline finished with Failed
    about 1 month ago
    Total: 92s
    #395919
  • Pipeline finished with Failed
    about 1 month ago
    Total: 89s
    #395931
  • Pipeline finished with Failed
    about 1 month ago
    Total: 87s
    #395932
  • Pipeline finished with Failed
    about 1 month ago
    Total: 97s
    #395938
  • Pipeline finished with Failed
    about 1 month ago
    Total: 123s
    #395940
  • 🇮🇹Italy mondrake 🇮🇹

    After some headache, now found the right regex to have sed adjust the paths of the generated baseline so it can be really just copy/pasted to the branch with no additional edit.

  • Pipeline finished with Success
    about 1 month ago
    #395946
  • Pipeline finished with Canceled
    about 1 month ago
    Total: 132s
    #396738
  • Pipeline finished with Failed
    about 1 month ago
    Total: 146s
    #396741
  • Pipeline finished with Success
    about 1 month ago
    Total: 2119s
    #397023
  • 🇳🇱Netherlands bbrala Netherlands

    I actually ran into this issue earlier today by chance (the paths not being correct).

    This looks good and will make some things easier, but also allow for a good interface in gitlab for changes as per 📌 [CI] Report PHPStan baseline statistics in job Active .

    All good, working as intended :)

  • The Needs Review Queue Bot tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

    This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

    Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.

  • 🇮🇹Italy mondrake 🇮🇹

    Please, bot, don't boycott.

  • Pipeline finished with Success
    about 1 month ago
    Total: 299s
    #400747
Production build 0.71.5 2024