Page MenuHomePhabricator
Create Task
Maniphest T172165

Require either PHP 7.0+ or HHVM in MW 1.31
Closed, ResolvedPublic
Actions

Assigned To
Jdforrester-WMF
Authored By
MaxSem
Aug 1 2017, 2:50 AM
Tags
Referenced Files
None
Subscribers
Addshore
Aklapper
alex-mashin
ArielGlenn
aude
bd808
cscott
View All 37 Subscribers
Tokens
"Love" token, awarded by Lucas_Werkmeister_WMDE."Like" token, awarded by Liuxinyu970226."Like" token, awarded by MacFan4000."Like" token, awarded by Florian."Like" token, awarded by Smalyshev."Like" token, awarded by Aleksey_WMDE."Like" token, awarded by Addshore."Mountain of Wealth" token, awarded by thiemowmde."Mountain of Wealth" token, awarded by Ricordisamoa.

Description

Current proposal

  • MediaWiki 1.31 will require either PHP 7.0 or later, or HHVM.
  • Developers will target the common subset of HHVM (with hhvm.php7.all = false) and PHP 7.0+.
  • CI will enforce the use of this common subset using phpcs and/or phan rules
  • These changes will be deferred until MediaWiki in WMF production is fully migrated to a compatible environment. See the subtasks of this RFC. The deadline for this work is April 1, 2018.

Rationale

Pingbacks

Current PHP version statistics (as of 2018-03-04) from install pingbacks (this feature was introduced in 1.28 so all this data is from the era when PHP 5.5 was required):

CountPHP version
164295.6
155667.0
86437.1
28705.5
13707.2

See also complete pingback statistics. From MW 1.29, there are more installations with PHP 7.0 than 5.6.

WMF

One obstacle is that while WMF uses HHVM for MediaWiki, some other services are using Zend PHP, so we can't bump the requirements until all appservers have been updated to Debian Stretch.

External support

PHP Security SupportDebian supportUbuntu supportFedora supportPHPUnit
PHP 5.5ended July 2016noneuntil April 2019 (Ubuntu 14 Trusty)noneended Feb 2017 (PHPUnit 4)
PHP 5.6until Dec 2018until April 2020 (Debian Jessie)noneended Aug 2017 (Fedora 24)ended Feb 2018 (PHPUnit 5)
PHP 7.0until Dec 2018until June 2022 (Debian Stretch)until April 2021 (Ubuntu 16 Xenial)until Dec 2017 (Fedora 25)until Feb 2019 (PHPUnit 6)
PHP 7.1until Dec 2019futurefutureuntil Aug 2018 (Fedora 26)future

PHPUnit support: We're currently using PHPUnit 4.x (https://phpunit.de/), and have to because we run the tests on PHP 5.5 in CI and newer PHPUnit versions require at least PHP 5.6.

PHPUnit 4Supported PHP 5.3 - PHP 5.6No longer supported (March 2014 - Feb 2017)
PHPUnit 5Supports PHP 5.6 - PHP 7.1Legacy support (Oct 2015 - Feb 2018)
PHPUnit 6Supports PHP 7.0 - PHP 7.1Current stable (Feb 2017 - Feb 2019)

PHP Security support: http://php.net/supported-versions.php, http://php.net/eol.php

Distro support: https://wiki.debian.org/LTS, https://wiki.ubuntu.com/Releases, https://fedoraproject.org/wiki/End_of_life, https://apps.fedoraproject.org/packages/php

MediaWiki version lifecycle

https://www.mediawiki.org/wiki/Version_lifecycle / https://www.mediawiki.org/wiki/Compatibility

ReleasePHPEOL
MediaWiki 1.27 LTSPHP 5.5 - 7.1June 2019
MediaWiki 1.28PHP 5.5 - 7.0November 2017
MediaWiki 1.29PHP 5.5 - 7.1July 2018
MediaWiki 1.30PHP 5.5 - 7.1November 2018
MediaWiki 1.31 LTSTBDJune 2021

See also:

Details

SubjectRepoBranchLines +/-
Don't run php55 jobs on master (REL1_32) or wmf/ branchesintegration/configmaster+6 -5
Bump PHP version requirement to 7.0.0+mediawiki/coremaster+12 -120
Bump PHP version requirement to 7.0.0+mediawiki/coreREL1_31+13 -121
Customize query in gerrit

Related Objects
Search...

StatusSubtypeAssignedTask
 ResolvedJdforrester-WMFT172165 Require either PHP 7.0+ or HHVM in MW 1.31
 ResolvedfgiunchediT146285 Switch mwscript from Zend PHP5 to default php alternative (e.g. HHVM or PHP7)
 ResolvedPRODUCTION ERROREBernhardsonT132751 "Elastica: missing curl_init_pooled method" due to mwscript job running with PHP 5 on terbium
 ResolvedKrenairT125540 New version of File:Duniya Na Mane, 1937.webm
 ResolvedNoneT25748 Bad label on upload max filesize at upload page in spanish version
 ResolvedhasharT146286 mwscript on jessie mediawiki fails
 ResolvedtstarlingT145819 Jobs invoking SiteConfiguration::getConfig cause HHVM to fail updating the bytecode cache due to being filesize limited to 512MBytes
 ResolvedtstarlingT111441 SiteConfiguration::getConfig() does not work in Wikimedia production
 ResolvedArielGlennT181029 Upgrade dump hosts to stretch with php7
 ResolvedArielGlennT161509 Test php7 on snapshot1001 for dumps
 ResolvedArielGlennT193399 Test all misc dumps cron jobs on snapshot1001 with php7/stretch
 ResolvedArielGlennT184258 get a snapshot instance running in beta with stretch, php7
 ResolvedNoneT184854 hhvm memcached and php7 memcached extensions do not play well together
 ResolvedLegoktmT184270 rebuild php-wikidiff2 and php-luasandbox for php7 and stretch
 ResolvedPRODUCTION ERRORAndrewT168470 Setup wikitech, horizon, and striker on new labweb hardware
 ResolvedAndrewT98813 Move wikitech (silver) to HHVM
 ResolvedAndrewT167820 rack/setup/install labweb100[12].wikimedia.org
 ResolvedAndrewT186729 labweb1001 and 1002 need to access labnet1001.eqiad.wmnet:8774 (and labnet1002.eqiad.wmnet:8774)
 ResolvedAndrewT187493 deploy horizon version 'ocata' using scap3
 ResolvedAndrewT187496 horizon puppet prefix tab creation broken
 ResolvedAndrewT187499 puppet tab class apply fails
 Resolvedbd808T187420 Graphics for wmcs/horizon branding
 ResolvedAndrewT187502 Update graphics and branding for horizon 'material' theme
 ResolvedAndrewT187506 load-balance horizon between labweb1001 and 1002
 ResolvedAndrewT187563 horizon deploy fails at the very end "Port 8080 not up. Waiting 3.00s"
 ResolvedAndrewT187810 horizon 'reverse dns' panel throws lots of errors, probably useless
 ResolvedAndrewT187811 horizon: language selection broken
 ResolvedAndrewT187743 Deploy striker on labweb1001, 1002
 ResolvedAndrewT188029 Move labswiki database to m5
ResolvedAndrewT188458 Newhorizon errors on sudo policy changes
 ResolvedAndrewT188915 Move wikitech images to swift
 ResolvedAndrewT188926 New wikitech-static sync process for images
 ResolvedAndrewT189168 How to purge misc-web varnishes for wikitech changes?
 ResolvedAndrewT189278 Session issues on labweb horizon ('newhorizon.wikimedia.org')
 ResolvedPRODUCTION ERRORAndrewT189347 Possible issues with varnish purging on wikitech
 ResolvedMaxSemT177273 avro-php tests fail under PHP 7
 ResolvedLegoktmT190547 Make Wikimedia CI run PHP in either PHP 7.0+ or HHVM
 ResolvedLegoktmT190548 Update mediawiki-core-qunit-selenium-jessie/mediawiki-extensions-qunit-jessie jobs from PHP5 to PHP7/HHVM
 ResolvedLegoktmT147778 Switch MediaWiki coverage job from PHP 5 to PHP 7
 ResolvedNoneT147781 MediaWiki code coverage fails on Zend PHP 7.0 due to a database error
 ResolvedPRODUCTION ERRORAnomieT191863 SearchEngineTest fails during PHPUnit coverage job "no such table: unittest_page"
 Resolved• ImarlierT184638 Identify uses of Zend PHP5 in Wikimedia production
 ResolvedNoneT195393 Run all maintenance scripts on PHP7 or HHVM
 ResolvedDzahnT192092 setup replacements for maintenance_server (terbium, wasat) on Stretch
 ResolvedRobHT192185 request to assign spare systems as terbium equivalent
 Resolved• CmjohnsonT193798 change hostname label for mw1297 to mwmaint1001
 ResolvedMoritzMuehlenhoffT193915 rename wasat to mwmaint2001 and reinstall it with stretch
 ResolvedPapaulT199530 Rename of wasat to mwmaint2001 (switch labels et al)
 ResolvedSmalyshevT204389 Update wasat/mwmaint2001 docs on Wikitech
 Resolved• jcrespoT193919 provide proxysql for stretch, add package to puppet
 ResolvedJdforrester-WMFT198805 Update wikitech docs to use new mwmaint1001 instead of terbium

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes
Legoktm removed a parent task: T177132: Run MediaWiki tests with PHPUnit 6.Feb 19 2018, 6:57 PM
Legoktm mentioned this in T177132: Run MediaWiki tests with PHPUnit 6.
Krinkle mentioned this in T150912: Class 'Memcached' not found when running mwscript eval.php on debug servers.Feb 20 2018, 5:02 AM
Jdforrester-WMF added a subtask: T177273: avro-php tests fail under PHP 7.Feb 26 2018, 4:57 PM
Andrew mentioned this in Blog Post: Running red-queen-style.Mar 9 2018, 11:13 PM
Seb35 updated the task description. (Show Details)Mar 13 2018, 1:30 PM
• demon closed subtask T146285: Switch mwscript from Zend PHP5 to default php alternative (e.g. HHVM or PHP7) as Resolved.Mar 14 2018, 4:37 PM
Jdforrester-WMF mentioned this in T86081: Complete the use of HHVM over Zend PHP on the Wikimedia cluster.Mar 21 2018, 12:10 AM
Jdforrester-WMF mentioned this in T117534: DCAT-AP: XML produces invalid output with HHVM.
Krinkle reopened subtask T146285: Switch mwscript from Zend PHP5 to default php alternative (e.g. HHVM or PHP7) as Open.Mar 21 2018, 3:27 AM
Andrew closed subtask T168470: Setup wikitech, horizon, and striker on new labweb hardware as Resolved.Mar 21 2018, 7:33 PM
Krinkle removed a parent task: T181931: MediaWiki PHPUnit fails with PHP 7.2.Mar 24 2018, 1:53 AM
Jdforrester-WMF added a project: MW-1.31-release.Mar 27 2018, 9:28 PM
Jdforrester-WMF closed subtask T177273: avro-php tests fail under PHP 7 as Resolved.Mar 29 2018, 7:37 PM
Krinkle closed subtask T146285: Switch mwscript from Zend PHP5 to default php alternative (e.g. HHVM or PHP7) as Resolved.Apr 9 2018, 3:44 PM
Krinkle added subtasks: T94149: Get rid of Zend 5.5 tests for wmf branches, T184638: Identify uses of Zend PHP5 in Wikimedia production.Apr 9 2018, 4:06 PM
Krinkle removed a parent task: T178136: Encourage type hints for function parameters and return after moving MediaWiki to PHP 7.
Krinkle removed a subtask: T94149: Get rid of Zend 5.5 tests for wmf branches.Apr 9 2018, 4:11 PM
Krinkle added a subtask: T184854: hhvm memcached and php7 memcached extensions do not play well together.
Krinkle closed subtask T184638: Identify uses of Zend PHP5 in Wikimedia production as Resolved.
Krinkle removed a subtask: T165300: [Task] Drop PHP 5.3 and 5.4 support in all Wikidata code repositories.Apr 10 2018, 1:51 PM
thcipriani mentioned this in T191921: mwscript rebuildLocalisationCache.php takes 40 minutes on HHVM (rather than ~5 on PHP 5).Apr 10 2018, 9:26 PM
Liuxinyu970226 awarded a token.Apr 12 2018, 10:54 AM
Liuxinyu970226 subscribed.
Jdforrester-WMF added a parent task: T192166: Drop HHVM support from MediaWiki.Apr 13 2018, 6:29 PM
MGChecker subscribed.Apr 16 2018, 8:20 AM
Paladox added a comment.Apr 18 2018, 2:36 AM

Titile should be changed to Require PHP 7.0+ in MW 1.31?

Since we have decided that we are going with php 7+.

Krinkle added a comment.EditedApr 18 2018, 2:49 AM

That is incorrect. The title accurately reflects the RFC decision that we are implementing.

Legoktm closed subtask T190547: Make Wikimedia CI run PHP in either PHP 7.0+ or HHVM as Resolved.Apr 18 2018, 5:38 PM
gerritbot added a comment.Apr 18 2018, 6:00 PM

Change 427458 had a related patch set uploaded (by Jforrester; owner: Jforrester):
[mediawiki/core@REL1_31] Bump PHP version requirement to 7.0.0+

https://gerrit.wikimedia.org/r/427458

Krinkle moved this task from Backlog to Core on the MW-1.31-release board.Apr 18 2018, 6:08 PM
gerritbot added a comment.Apr 18 2018, 8:48 PM

Change 427458 merged by jenkins-bot:
[mediawiki/core@REL1_31] Bump PHP version requirement to 7.0.0+

https://gerrit.wikimedia.org/r/427458

ReleaseTaggerBot added a project: MW-1.31-release-notes.Apr 18 2018, 9:00 PM
Krinkle moved this task from In progress to Implemented on the TechCom-RFC (TechCom-RFC-Closed) board.Apr 18 2018, 9:51 PM
Krinkle removed a subtask: T184854: hhvm memcached and php7 memcached extensions do not play well together.Apr 18 2018, 10:49 PM
Krinkle removed a parent task: T192166: Drop HHVM support from MediaWiki.Apr 18 2018, 10:53 PM
RazeSoldier subscribed.Apr 19 2018, 12:04 AM
In T172165#4140726, @gerritbot wrote:

Change 427458 merged by jenkins-bot:
[mediawiki/core@REL1_31] Bump PHP version requirement to 7.0.0+

https://gerrit.wikimedia.org/r/427458

Does this mean that we can use the new features (new syntax) of PHP 7?

Krinkle added a comment.EditedApr 19 2018, 12:06 AM

@RazeSoldier No, not yet. It was merged in REL1_31 for the upcoming 1.31 release candidate, but not yet in master. Once it lands in master (should be a few weeks at most), the linter and style checker may be changed to allow newer syntax features.

EddieGP added a comment.Apr 19 2018, 12:09 AM

Also note that most of the new php7 syntax won't be available until we stop supporting hhvm. (T176370)

Jdforrester-WMF added a comment.Apr 19 2018, 12:45 AM

Technically this is now done (for MW 1.31), but I'm planning only to declare this actually Resolved once master is switched too.

Anomie added a comment.Apr 19 2018, 6:04 PM
In T172165#4141483, @EddieGP wrote:

Also note that most of the new php7 syntax won't be available until we stop supporting hhvm. (T176370)

HHVM supports many PHP7 features even when hhvm.php7.all or similar configuration options aren't set. A partial list is mentioned in T172165#3699606.

Smalyshev added a comment.Apr 19 2018, 8:47 PM

Should we have a formal list/guidelines of what is allowed and what is not, once the switch is done, somewhere on wiki? At least for the period when hhvm support is still required.

Reedy added a comment.Apr 19 2018, 9:01 PM
In T172165#4144241, @Smalyshev wrote:

Should we have a formal list/guidelines of what is allowed and what is not, once the switch is done, somewhere on wiki? At least for the period when hhvm support is still required.

Do remember master will be supporting PHP 5.5 for a little while longer too.

It may be easier to just keep PHP 7 features out till HHVM support is actually dropped... HHVM supports some, but we don't have php7 mode enabled (for backwards incompatible stuff)

Though, if tests run on HHVM pass..

Anomie added a comment.Apr 19 2018, 9:08 PM

I note we specifically did this "PHP 7.0+ or HHVM in MW 1.31" so we could start using the PHP7 features that HHVM does support. Once master drops PHP5, of course.

matmarex added a comment.Apr 19 2018, 9:30 PM

According to Anomie's previous comments (T172165#3699606), HHVM supports all PHP 7 syntax features, except where PHP 7 intentionally breaks compatibility with PHP 5 syntax: T173786#3651007.

Note that there are a few patches already pending that would introduce uses of some new features: https://gerrit.wikimedia.org/r/#/q/status:open+(topic:new-php+OR+topic:newphp). If you want to discuss disallowing specific features in our code conventions, now is probably time for it :)

MGChecker added a comment.Apr 19 2018, 11:34 PM

What exactly is blocking master to require PHP 7, if even 1.31 is already requiring it?

Paladox added a comment.Apr 19 2018, 11:39 PM

For it to be upgraded in wmf prod.

MGChecker added a comment.Apr 19 2018, 11:49 PM

Is there a date set when to do this? I assumed HHVM compatibility would cover our needs.

Reedy added a comment.Apr 20 2018, 7:36 AM
In T172165#4144737, @MGChecker wrote:

What exactly is blocking master to require PHP 7, if even 1.31 is already requiring it?

T181029#4142688 - Hopefully it should only be a couple of weeks

We've some hosts that still run 5.5, but we don't run 1.31 in production (and it's got a little while till being ready)

In T172165#4144790, @MGChecker wrote:

Is there a date set when to do this? I assumed HHVM compatibility would cover our needs.

HHVM supports PHP 7 features that PHP 5.5 doesn't, so we still can't have those as the hosts aren't running HHVM, they're running PHP 5.5.

So it's easiest to just keep master free (for now), rather than reverting in WMF branches and then potentially reverting extra patches.

It's coming, and it's nearly there. In the grand scheme of things, there's no major need to "rush" and start adding PHP 7 features everywhere, unless they bring reasonable gains from doing so... A few more weeks is nothing in the grand scheme of things :)

gh87 subscribed.EditedApr 20 2018, 8:03 AM

PHP 7.0 will be supported until December of this year: http://php.net/archive/2018.php#id2018-01-04-1

The task should be changed from "7.0+" to "7.1+", and Its "PHP Security Support" year should be corrected from "Dec 2019" to "Dec 2018".

Reedy added a comment.Apr 20 2018, 8:08 AM
In T172165#4145210, @gh87 wrote:

PHP 7.0 will be supported until December of this year: http://php.net/archive/2018.php#id2018-01-04-1

The task should be changed from "7.0+" to "7.1+", and the support end-year should be corrected from "Dec 2019" to "Dec 2018"

No, because that wasn't agreed on in the RfC.

In the same way we've supported other versions of unsupported PHP (like we currently do for PHP 5.5), we'll support PHP 7. Hosting providers don't upgrade quickly, and neither do many other sysadmins and users.

gh87 updated the task description. (Show Details)Apr 20 2018, 8:23 AM
• demon moved this task from Core to Done on the MW-1.31-release board.May 15 2018, 1:13 PM
ArielGlenn closed subtask T181029: Upgrade dump hosts to stretch with php7 as Resolved.May 20 2018, 9:15 AM
Reedy added a comment.May 20 2018, 10:10 AM

So can we merge https://gerrit.wikimedia.org/r/#/c/405216/ now? :D

ArielGlenn added a comment.EditedMay 22 2018, 9:47 AM

As mentioned a couple of days ago, some jobs on terbium are still running with php5; those are the jobs that run via foreachwiki as www-data which calls foreachwikiindblist.
A list of those jobs is here: P7139

There's two options.
One: fix foreachwikindblist so it doesn't use php5 but whatever /usr/bin/php points to, which on terbium would be hhvm. Someone(s) should feel confident that the above jobs run well on hhvm before such a change is deployed.
Two: wait for terbium's replacement (mwmaint1001) to become the live server. See T192092 This would happen sometime after the tin -> deploy1001 switchover, which is currently scheduled for May 25, see T175288#4205322 In this case, someone(s) should feel confident that the above jobs run well on php7.0.

Can folks discuss and get us a plan?

gh87 unsubscribed.May 22 2018, 10:11 AM
Jdforrester-WMF added a subtask: T195393: Run all maintenance scripts on PHP7 or HHVM.May 23 2018, 5:42 PM
Reedy mentioned this in T195393: Run all maintenance scripts on PHP7 or HHVM.May 23 2018, 6:09 PM
Joe closed subtask T195393: Run all maintenance scripts on PHP7 or HHVM as Resolved.May 24 2018, 2:15 PM
gerritbot added a comment.May 24 2018, 2:21 PM

Change 434922 had a related patch set uploaded (by Reedy; owner: Reedy):
[integration/config@master] Don't run php55 jobs on master (REL1_32)

https://gerrit.wikimedia.org/r/434922

gerritbot added a comment.May 24 2018, 3:13 PM

Change 434922 merged by jenkins-bot:
[integration/config@master] Don't run php55 jobs on master (REL1_32) or wmf/ branches

https://gerrit.wikimedia.org/r/434922

gerritbot added a comment.May 24 2018, 4:14 PM

Change 405216 merged by jenkins-bot:
[mediawiki/core@master] Bump PHP version requirement to 7.0.0+

https://gerrit.wikimedia.org/r/405216

Reedy closed this task as Resolved.May 24 2018, 4:19 PM
Reedy assigned this task to Jdforrester-WMF.
Reedy removed a project: Patch-For-Review.

Boom

Jdforrester-WMF added a comment.May 24 2018, 4:35 PM

Gosh.

Lucas_Werkmeister_WMDE awarded a token.May 24 2018, 4:49 PM
ReleaseTaggerBot added a project: MW-1.32-notes (WMF-deploy-2018-05-29 (1.32.0-wmf.6)).May 24 2018, 5:00 PM
Jdforrester-WMF added a parent task: T192166: Drop HHVM support from MediaWiki.May 24 2018, 5:28 PM
JeroenDeDauw subscribed.May 25 2018, 2:25 PM

Will WMF be able to run (full) PHP 7.1 any time soon? (Note: I am not asking about bumping MW to 7.1, just when WMF will be able to run it.)

Reedy added a comment.May 25 2018, 2:53 PM
In T172165#4231598, @JeroenDeDauw wrote:

Will WMF be able to run (full) PHP 7.1 any time soon? (Note: I am not asking about bumping MW to 7.1, just when WMF will be able to run it.)

I don’t think so. Depends when next Debian stable has 7.1, and the next round of reinstalls happen...

EddieGP added a comment.EditedMay 25 2018, 2:54 PM
In T172165#4231598, @JeroenDeDauw wrote:

Will WMF be able to run (full) PHP 7.1 any time soon? (Note: I am not asking about bumping MW to 7.1, just when WMF will be able to run it.)

See T176370: Migrate to PHP 7 in WMF production. WMF is currently migrating to PHP7.0 aiui.

JeroenDeDauw added a comment.EditedMay 28 2018, 9:18 PM

That is the issue I came from actually.

Question 1: So WMF is definitely going to 7.0 and not 7.1 or 7.2?!
Question 2: When will WMF be able to run full PHP 7.0?

Paladox added a comment.May 28 2018, 9:54 PM

I think there planning to do 7.2 (that’s what was discussed when copying the php 7.2 packages over for phabricator).

But they will be going to php 7.0 first.

Reedy added a comment.May 28 2018, 9:58 PM
In T172165#4237401, @JeroenDeDauw wrote:

That is the issue I came from actually.

Question 1: So WMF is definitely going to 7.0 and not 7.1 or 7.2?!
Question 2: When will WMF be able to run full PHP 7.0?

Why are you asking the same questions on numerous different tasks?

In T176370#4234207, @Reedy wrote:
In T176370#4234205, @JeroenDeDauw wrote:

Any ETA on when WMF will be able to run full PHP 7.0? And will it be running PHP 7.0 or a more recent version of 7.x?

7.0.27-0+deb9u1

Because Debian Stretch.

https://packages.debian.org/stretch/php7.0

JeroenDeDauw added a comment.May 29 2018, 9:20 PM

Why are you asking the same questions on numerous different tasks?

Because I got linked here and still did not get a clear answer. As in: still not. "7.0.27-0+deb9u1" is not a date and I do not know how to translate it to one.

So:

Question 1: So WMF is definitely going to 7.0 and not 7.1 or 7.2?!
Question 2: When will WMF be able to run full PHP 7.0?

Reedy added a comment.May 29 2018, 9:27 PM
In T172165#4241326, @JeroenDeDauw wrote:

Why are you asking the same questions on numerous different tasks?

Because I got linked here and still did not get a clear answer. As in: still not. "7.0.27-0+deb9u1" is not a date and I do not know how to translate it to one.

You were also asking the question around/on a long holiday weekend. Patience might be needed to get full/proper responses. People do have lives and time off.

Try also reading the responses to your questions, and the tasks/comments they link

In T176370#4234208, @Reedy wrote:

T174431#4198574

Should be a few weeks before we have PHP 7 available everywhere.

There's still work to move from hhvm to PHP7 for actual production

It's going to be 7.0.X initially, at least, yes. 7.1/7.2 will come sometime in the future (possibly with OS upgrades, possibly before).

We're waiting on a couple more hosts being migrated away from having PHP5 to having PHP 7, this is due to be finished off shortly

And define "full PHP 7.0"? There's some divergence between PHP7 and HHVM. So, the functionality that HHVM implements differently. So, while HHVM is still in use, PHP7 functionality that isn't in HHVM (or differently implemented) cannot be used.

Reedy added a comment.May 29 2018, 9:33 PM
In T172165#4241326, @JeroenDeDauw wrote:

Question 1: So WMF is definitely going to 7.0 and not 7.1 or 7.2?!

And all that aside, MW needs to be 7.0 compatible (as per the RfC), so it doesn't matter if WMF is running 7.1 or 7.2

Krinkle added a comment.EditedMay 29 2018, 9:34 PM
In T172165#4241326, @JeroenDeDauw wrote:

Question 1: So WMF is definitely going to 7.0 and not 7.1 or 7.2?!

Yes, that was decided last year and is what everyone's been working on. The Debian upgrade is already underway, and there probably isn't enough reason to re-allocate existing bandwidth and priorities from other projects to do a second Debian-PHP migration this/next quarter.

More about this at T176370: Migrate to PHP 7 in WMF production.

Question 2: When will WMF be able to run full PHP 7.0?

Per:
https://www.mediawiki.org/wiki/Wikimedia_Technology/Goals/2017-18_Q4#Technology_departmental_programs

Current quarter is:

  • Phase out all use of PHP 5.
  • Upgrade production app servers from Debian Jessie to Stretch (still with HHVM).
  • Switch some servers to PHP 7 (Beta Cluster, and deployment/maintenance hosts).

Running PHP 7 for the main application servers requires other preparations to be in place first. Including profiling, logging and error handling, which various teams are also working on this quarter so that later this year we can consider switching application servers from HHVM to PHP 7.

More about this at T176370.

RazeSoldier added a comment.Jun 1 2018, 12:48 PM

Now, can we define Array constants with define()? It is a new feature of PHP 7.

Reedy added a comment.Jun 1 2018, 12:54 PM
In T172165#4248579, @RazeSoldier wrote:

Now, can we define Array constants with define()? It is a new feature of PHP 7.

As long as they are features that don't require HHVM's PHP 7 mode to be on

See https://docs.hhvm.com/hhvm/configuration/INI-settings#php-7-settings for more information

Liuxinyu970226 unsubscribed.Jun 2 2018, 2:10 PM
• Vvjjkkii reopened subtask T195393: Run all maintenance scripts on PHP7 or HHVM as Open.Jul 1 2018, 1:08 AM
ArielGlenn closed subtask T195393: Run all maintenance scripts on PHP7 or HHVM as Resolved.Jul 1 2018, 8:24 AM
Krinkle mentioned this in T189631: deployment-tin: scripts taking a whole lot more of time to complete.Jul 6 2018, 11:46 PM
Ejegg mentioned this in T201540: PHP on Debian after 12/2018.Aug 9 2018, 1:49 AM
Krinkle removed a parent task: T192166: Drop HHVM support from MediaWiki.Aug 29 2018, 2:37 AM
Krinkle mentioned this in T192166: Drop HHVM support from MediaWiki.
thiemowmde mentioned this in T213410: Start using PHP 7.0 features in WMDE maintained extensions.Jan 10 2019, 11:21 AM
Lucas_Werkmeister_WMDE mentioned this in T214161: wikidata-dev wikidata-lexeme instance has been found to be running an unsupported operating system.Jan 21 2019, 10:41 AM
Tgr mentioned this in T257879: Drop PHP 7.2 support in MediaWiki 1.35; require PHP 7.3.19.Jul 14 2020, 11:21 AM
Aklapper removed subscribers: • Imarlier, • ksmith, Anomie.Oct 16 2020, 5:42 PM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits