[wp-trac] [WordPress Trac] #53945: Local test workflow changes for installing Composer dependencies

[WordPress Trac]

#53945: Local test workflow changes for installing Composer dependencies
------------------------------------------------+--------------------------
 Reporter:  hellofromTonya                      |       Owner:  johnbillion
     Type:  task (blessed)                      |      Status:  reopened
 Priority:  normal                              |   Milestone:  5.9
Component:  Build/Test Tools                    |     Version:
 Severity:  normal                              |  Resolution:
 Keywords:  has-patch has-testing-instructions  |     Focuses:
------------------------------------------------+--------------------------

Comment (by jrf):

 Replying to [comment:31 azaozz]:
 > Right. I'm also noticing a delay of about 2.5-3 min every time the tests
 are run with `npm run test:php` or `npm run test:php-composer`. It happens
 after `Use the 'composer fund' command to find out more!` so presuming
 after composer has checked for updates. However skipping `composer update
 -W` and running only `% node ./tools/local-env/scripts/docker.js run --rm
 phpunit phpunit "--group" "formatting"` doesn't trigger that delay.
 >
 > That ~3 min delay is pretty annoying especially when writing or fixing
 tests and running the same test 10-20 times in a row. Even if it's fixed,
 perhaps Composer updates should not be running every time PHPUnit is run,
 still takes 5-10 sec to check :)

 The delay happening **after** the "composer fund" to me indicates that
 this has nothing to do with Composer as Composer is already finished by
 then.

 If I remember correctly, I believe @johnbillion also mentioned something
 about running the tests via Docker being significantly slower
 (independently of this change and before this change was even made). He
 also mentioned a time difference of ~3 minutes.

 So, yes, that must be really annoying, but I somehow have a feeling that
 that delay is unrelated to what we're doing in this ticket.

 The ~3 minute delay sounds like a 180 second process timeout, so I wonder
 whether there is something going on in Docker where either a process is
 not passing an exit code and the script is waiting for one or where the
 exit code is not being checked correctly. Just guessing here, but might be
 a starting point for debugging this.

 Either way, the delay sounds like something which most likely has nothing
 to do with Composer and is outside of the scope of this ticket.

 I think a separate ticket needs to be opened to look into debugging that.

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