[wp-trac] [WordPress Trac] #62176: No stable error detection after Automatic Updates with more than one update

[WordPress Trac]

#62176: No stable error detection after Automatic Updates with more than one update
-------------------------------------------------+-------------------------
 Reporter:  georgwordpress                       |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Upgrade/Install                      |     Version:  6.6
 Severity:  normal                               |  Resolution:
 Keywords:  2nd-opinion has-patch reporter-      |     Focuses:
  feedback                                       |
-------------------------------------------------+-------------------------
Changes (by costdev):

 * keywords:  2nd-opinion has-patch => 2nd-opinion has-patch reporter-
               feedback


Comment:

 Hi @georgwordpress, thanks for opening this ticket!

 A few things I'd recommend before we consider the PR:

 1. This should be tested on a clean installation, with the exception of at
 least two plugins that will fatal on update.
 2. The automatic updater should run as normal. It should not be triggered
 manually or through any other trigger.
 3. We'll need to get full environment information to ensure we track
 similarities between environments that can reproduce this issue.
 4. We need to see a log of the whole process that demonstrates which
 plugin is being updated at that time, what its expected `$upgrading` value
 should be and what the actual `$upgrading` value is. This will allow us to
 see this mismatch in the full context of an update run for multiple
 plugins.

 Update processes ''can'' be triggered manually/via other triggers, and
 sites may not be clean installations. At this stage of testing, reducing
 all this to the base functionality helps us determine what causes this to
 occur when thousands of tests prior to the feature's release didn't
 produce this. The issue is of course happening, so now we need to identify
 the specific cause(s). It may be certain environmental conditions, testing
 conditions, or something else that explains why pre-release testing was
 fine, but this post-release testing is not.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/62176#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform