Page MenuHomePhabricator

LibUp fails to submit patches despite seemingly running without error
Closed, InvalidPublicBUG REPORT

Description

Steps to replicate the issue (include links if applicable):

  • LibUp detected one outdated composer dependency for CommunityConfiguration (php-parallel-lint/php-parallel-lint from 1.3.2 to 1.4.0) and prepared a patch for it: https://libraryupgrader2.wmcloud.org/logs2/1295003
  • The LibUp script seeming ran without error (see log at the above link)
  • The prepared change has the Change-Id: If92d1a0187ec5c8a095b0b406cb5e5bf02576787

What happens?:

What should have happened instead?:

  • There should be a LibUp change that updates php-parallel-lint/php-parallel-lint

Notes:

Event Timeline

taavi subscribed.

The weight configured for php-parallel-lint is low enough that LibUp will only push that when there's something else to update with it.

The weight configured for php-parallel-lint is low enough that LibUp will only push that when there's something else to update with it.

Thank you for sharing this! This policy makes sense, but I wonder if it could also be mentioned in the log of a run?