Make WordPress Core

Changes between Version 2 and Version 3 of Ticket #53945, comment 41


Ignore:
Timestamp:
09/13/2021 10:49:40 PM (2 years ago)
Author:
azaozz
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #53945, comment 41

    v2 v3  
    66> on the first run it was about 18-20 seconds and on average about 1.5 seconds for rerunning tests over and over again.
    77
    8 Yeah, the numbers here are similar: 20-25 sec. on the first run, then the longer delay after Composer and before PHPUnit (more like 50-60 seconds now). Running the tests again, the delays are a lot smaller. Tried to figure out what's going on and it looks like npm is running some update checks (perhaps) as it is making ~200-300 requests during that first-run delay.
     8Yeah, the numbers here are similar: 20-25 sec. on the first run, then the longer delay after Composer and before PHPUnit (more like 50-60 seconds now). Running the tests again, the delays are a lot smaller.
     9
     10Tried to figure out what's going on and it looks like npm is running some update checks (perhaps) as it is making few hundreds requests during that first-run delay. Seems that's from the `Creating trunk-wpenv_phpunit_run ... done` and `Installing...`:
     11
     12{{{
     13...
     1426 packages you are using are looking for funding.
     15Use the `composer fund` command to find out more!
     16Creating trunk-wpenv_phpunit_run ... done
     17Installing...
     18Running as single site... To run multisite, use -c tests/phpunit/multisite.xml
     19Not running ajax tests. To execute these, use --group ajax.
     20...
     21}}}
    922
    1023Another thing I've noticed is that `npm run test:php` will fail if the network connection is shaky/faulty and Composer is not able to check for updates. It also fails on subsequent runs when there will be no updates available. The PHP tests (mostly) run with no internet connection (although some fail instead of being skipped). Not a big deal but may be good to fix.