[00:00:20] 10Gerrit, 103d: Create repo for extension 3d and import into gerrit - https://phabricator.wikimedia.org/T158881#3066227 (10Jdforrester-WMF) 05Open>03Resolved a:03Jdforrester-WMF Now done. [01:26:16] Project beta-scap-eqiad build #144583: 04FAILURE in 1 min 24 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144583/ [01:36:17] Project beta-scap-eqiad build #144584: 04STILL FAILING in 1 min 22 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144584/ [01:46:14] Project beta-scap-eqiad build #144585: 04STILL FAILING in 1 min 22 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144585/ [01:56:43] Yippee, build fixed! [01:56:44] Project beta-scap-eqiad build #144586: 09FIXED in 1 min 54 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144586/ [02:10:48] Hello. I would like to have Doxygen and JSDuck automatically generate documentation for my extension for publication on doc.wikimedia.org. There is technically documentation of this but it does not get me any closer to figuring out how to actually do this. Can someone advise? [02:26:11] Project beta-scap-eqiad build #144589: 04FAILURE in 1 min 22 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144589/ [02:36:06] Project beta-scap-eqiad build #144590: 04STILL FAILING in 1 min 20 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144590/ [02:46:11] Project beta-scap-eqiad build #144591: 04STILL FAILING in 1 min 22 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144591/ [02:56:39] Yippee, build fixed! [02:56:39] Project beta-scap-eqiad build #144592: 09FIXED in 1 min 50 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144592/ [03:06:22] 06Release-Engineering-Team, 10Monitoring, 06Operations, 07Tracking, 07Wikimedia-Incident: Tracking: Monitoring and alerts for "business" metrics - https://phabricator.wikimedia.org/T140942#2481685 (10Tbayer) The alert feature introduced in the recent Grafana update (T152473) could be of interest for this... [03:12:33] RECOVERY - Long lived cherry-picks on puppetmaster on deployment-puppetmaster02 is OK: OK: Less than 100.00% above the threshold [0.0] [04:00:41] (03CR) 10Aude: [C: 031] "this seems safer to do for now. (than updating to 1.3.*)" [integration/composer] - 10https://gerrit.wikimedia.org/r/339645 (https://phabricator.wikimedia.org/T125343) (owner: 10Hashar) [05:01:45] 06Release-Engineering-Team, 10MediaWiki-Configuration, 13Patch-For-Review, 06Services (watching): Automate WMF wiki creation - https://phabricator.wikimedia.org/T158730#3066702 (10Krinkle) [05:28:33] 10Continuous-Integration-Config, 10ContentTranslation, 03Language-2017 Sprint 2, 03Language-2017 Sprint 3, and 3 others: mwext-qunit-jessie test fails on unrelated change - https://phabricator.wikimedia.org/T153038#3066736 (10KartikMistry) @mmodell Yes. https://gerrit.wikimedia.org/r/#/q/82f5a0be38e9bef98a... [05:53:21] 06Release-Engineering-Team, 10MediaWiki-Configuration, 13Patch-For-Review, 06Services (watching): Automate WMF wiki creation - https://phabricator.wikimedia.org/T158730#3045487 (10GWicke) Much of this should be doable with our regular config management system. With puppet the deployment part however is not... [06:09:32] PROBLEM - Free space - all mounts on deployment-fluorine02 is CRITICAL: CRITICAL: deployment-prep.deployment-fluorine02.diskspace._srv.byte_percentfree (<10.00%) [06:54:32] RECOVERY - Free space - all mounts on deployment-fluorine02 is OK: OK: All targets OK [07:03:10] PROBLEM - Puppet run on deployment-imagescaler01 is CRITICAL: CRITICAL: 100.00% of data above the critical threshold [0.0] [07:56:17] Project beta-scap-eqiad build #144622: 04FAILURE in 1 min 24 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144622/ [08:04:59] 10Continuous-Integration-Config, 10ContentTranslation, 03Language-2017 Sprint 2, 03Language-2017 Sprint 3, and 3 others: mwext-qunit-jessie test fails on unrelated change - https://phabricator.wikimedia.org/T153038#3066848 (10mmodell) @kartikmistry: Agreed, I was just trying to assess the urgency of gettin... [08:06:10] Project beta-scap-eqiad build #144623: 04STILL FAILING in 1 min 21 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144623/ [08:08:23] weird, the build failure is scap saying host key verification failed for a bunch of hosts [08:16:17] Project beta-scap-eqiad build #144624: 04STILL FAILING in 1 min 20 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144624/ [08:18:56] ok puppet updated all the host keys and apparently broke things somehow [08:19:05] err, it updated the known_hosts file [08:26:41] Yippee, build fixed! [08:26:42] Project beta-scap-eqiad build #144625: 09FIXED in 1 min 51 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144625/ [08:37:05] Hello people! [08:37:23] I am going to upgrade apache on all the deployment-prep mediawiki instances [08:37:41] this version contain the last security upgrades from the Debian DSA [08:38:11] it is kinda invasive since it introduces a new directive called HttpProtocolOptions (https://httpd.apache.org/docs/2.4/mod/core.html#httpprotocoloptions) [08:38:24] it is enforced by default if not specified [08:38:58] and it is meant to block HTTP requests considered malformed (considering the last HTTP RFC) [08:39:04] preventing request splitting, etc.. [08:39:15] so best case scenario, nothing happens and we are goot [08:39:18] *good [08:39:28] worst case, you'll see HTTP 400 responses [08:39:37] and we'll need to track down what is failing [08:40:32] !log upgrading apache2 on deployment-mediawiki* - latest debian DSA, introduces https://httpd.apache.org/docs/2.4/mod/core.html#httpprotocoloptions (risk of HTTP 400 responses regression, contact elukey or moritzm if you see any issue) [08:40:35] Logged the message at https://wikitech.wikimedia.org/wiki/Release_Engineering/SAL [09:15:36] (03CR) 10Hashar: [C: 032] "Lets unleash that one and see what happens." [integration/composer] - 10https://gerrit.wikimedia.org/r/339645 (https://phabricator.wikimedia.org/T125343) (owner: 10Hashar) [09:15:48] (03Merged) 10jenkins-bot: Update composer to 1.1.0 with composer 1.1.0/PHP 5.5 [integration/composer] - 10https://gerrit.wikimedia.org/r/339645 (https://phabricator.wikimedia.org/T125343) (owner: 10Hashar) [09:16:35] !log upgrade composer to 1.1.0 https://gerrit.wikimedia.org/r/#/c/339645/ [09:16:37] Logged the message at https://wikitech.wikimedia.org/wiki/Release_Engineering/SAL [09:18:02] !log upgrading composer on permanent slaves for T125343 : salt -v '*slave*' cmd.run 'cd /srv/deployment/integration/composer && git pull' [09:18:05] Logged the message at https://wikitech.wikimedia.org/wiki/Release_Engineering/SAL [09:18:05] T125343: Upgrade integration/composer to 1.3.2 stable - https://phabricator.wikimedia.org/T125343 [09:29:26] !log Image snapshot-ci-trusty-1488446586 in wmflabs-eqiad is ready [09:29:29] Logged the message at https://wikitech.wikimedia.org/wiki/Release_Engineering/SAL [09:46:46] 10Browser-Tests-Infrastructure, 10Wikidata, 07Tracking: [DO NOT USE] Wikidata Browsertests (tracking) [superseded by #Browser-Tests] - https://phabricator.wikimedia.org/T88541#3067059 (10Liuxinyu970226) [09:53:30] !log Image snapshot-ci-jessie-1488447340 in wmflabs-eqiad is ready [09:53:32] Logged the message at https://wikitech.wikimedia.org/wiki/Release_Engineering/SAL [10:26:27] Project beta-scap-eqiad build #144637: 04FAILURE in 1 min 30 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144637/ [10:36:18] Project beta-scap-eqiad build #144638: 04STILL FAILING in 1 min 22 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144638/ [10:45:27] 10Continuous-Integration-Config, 10Wikidata, 13Patch-For-Review, 03Wikidata-Sprint: Fatal error: Call to undefined function Wikibase\Client\Tests\RecentChanges\both() - on jenkins - https://phabricator.wikimedia.org/T158674#3067306 (10hashar) I got composer upgraded to 1.1.0 which let us merge the extra s... [10:46:22] Project beta-scap-eqiad build #144639: 04STILL FAILING in 1 min 28 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144639/ [10:51:20] 10Continuous-Integration-Infrastructure, 07Composer: Upgrade of composer to v1.1.0 breaks some builds - https://phabricator.wikimedia.org/T159431#3067313 (10hashar) [10:52:26] 10Continuous-Integration-Infrastructure, 07Composer: Upgrade of composer to v1.1.0 breaks some builds - https://phabricator.wikimedia.org/T159431#3067328 (10hashar) [11:03:21] (03PS1) 10Hashar: mw-fetch-composer-dev: make xargs verbose [integration/jenkins] - 10https://gerrit.wikimedia.org/r/340708 [11:04:25] (03CR) 10Hashar: [C: 032] mw-fetch-composer-dev: make xargs verbose [integration/jenkins] - 10https://gerrit.wikimedia.org/r/340708 (owner: 10Hashar) [11:05:21] (03Merged) 10jenkins-bot: mw-fetch-composer-dev: make xargs verbose [integration/jenkins] - 10https://gerrit.wikimedia.org/r/340708 (owner: 10Hashar) [11:07:24] 10Continuous-Integration-Infrastructure, 07Composer: Upgrade of composer to v1.1.0 breaks some builds - https://phabricator.wikimedia.org/T159431#3067383 (10Paladox) @hashar this is fixed in composer 1.1.1, see https://github.com/composer/composer/issues/5346 [11:08:53] 10Continuous-Integration-Infrastructure, 07Composer: Upgrade of composer to v1.1.0 breaks some builds - https://phabricator.wikimedia.org/T159431#3067414 (10Paladox) We should upgrade to the latest 1.1.x release and then to 1.3.x. [11:12:41] Yippee, build fixed! [11:12:42] Project beta-scap-eqiad build #144640: 09FIXED in 17 min: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144640/ [11:13:08] (03PS1) 10Hashar: composer-dev-args: spurt exception to stderr [integration/jenkins] - 10https://gerrit.wikimedia.org/r/340710 (https://phabricator.wikimedia.org/T159431) [11:14:58] 10Continuous-Integration-Infrastructure, 07Composer, 13Patch-For-Review: Upgrade of composer to v1.1.0 breaks some builds - https://phabricator.wikimedia.org/T159431#3067438 (10hashar) operations-mw-config-composer-hhvm-jessie does: node /srv/deployment/integration/slave-scripts/tools/composer-dev-args.... [11:21:26] (03PS1) 10Hashar: [mediawiki-config] verbose xargs for mw-fetch-composer-dev [integration/config] - 10https://gerrit.wikimedia.org/r/340712 (https://phabricator.wikimedia.org/T159431) [11:25:23] (03PS1) 10Hashar: [mediawiki-config] use full path to composer.json [integration/config] - 10https://gerrit.wikimedia.org/r/340713 (https://phabricator.wikimedia.org/T159431) [11:35:25] 10Continuous-Integration-Config, 10Wikidata, 13Patch-For-Review, 03Wikidata-Sprint: Fatal error: Call to undefined function Wikibase\Client\Tests\RecentChanges\both() - on jenkins - https://phabricator.wikimedia.org/T158674#3067465 (10hashar) Breakage of other builds is {T159431} [11:35:28] (03CR) 10Hashar: [C: 032] [mediawiki-config] verbose xargs for mw-fetch-composer-dev [integration/config] - 10https://gerrit.wikimedia.org/r/340712 (https://phabricator.wikimedia.org/T159431) (owner: 10Hashar) [11:35:29] 10Continuous-Integration-Infrastructure, 07Composer, 13Patch-For-Review: Upgrade of composer to v1.1.0 breaks some builds - https://phabricator.wikimedia.org/T159431#3067313 (10hashar) For operations/mediawiki-config we have not been using the `require-dev` from its composer.json. It never worked and we ende... [11:35:33] (03CR) 10Hashar: [C: 032] [mediawiki-config] use full path to composer.json [integration/config] - 10https://gerrit.wikimedia.org/r/340713 (https://phabricator.wikimedia.org/T159431) (owner: 10Hashar) [11:35:52] (03CR) 10Hashar: [C: 032] composer-dev-args: spurt exception to stderr [integration/jenkins] - 10https://gerrit.wikimedia.org/r/340710 (https://phabricator.wikimedia.org/T159431) (owner: 10Hashar) [11:37:07] (03Merged) 10jenkins-bot: [mediawiki-config] verbose xargs for mw-fetch-composer-dev [integration/config] - 10https://gerrit.wikimedia.org/r/340712 (https://phabricator.wikimedia.org/T159431) (owner: 10Hashar) [11:37:09] (03Merged) 10jenkins-bot: [mediawiki-config] use full path to composer.json [integration/config] - 10https://gerrit.wikimedia.org/r/340713 (https://phabricator.wikimedia.org/T159431) (owner: 10Hashar) [11:37:37] (03Merged) 10jenkins-bot: composer-dev-args: spurt exception to stderr [integration/jenkins] - 10https://gerrit.wikimedia.org/r/340710 (https://phabricator.wikimedia.org/T159431) (owner: 10Hashar) [11:47:43] 10Continuous-Integration-Infrastructure, 07Composer, 13Patch-For-Review: Upgrade integration/composer to 1.3.2 stable - https://phabricator.wikimedia.org/T125343#3067530 (10hashar) [11:47:45] 10Continuous-Integration-Infrastructure, 07Composer, 13Patch-For-Review: Upgrade of composer to v1.1.0 breaks some builds - https://phabricator.wikimedia.org/T159431#3067528 (10hashar) 05Open>03Resolved Fixed by using an absolute paths to composer.json. As a side effect enhanced composer-fetch-dev to be... [11:52:42] !log gerrit: killed a stalled connection: dd511e52 Feb-27 07:11 git-receive-pack '/mediawiki/services/zotero/translators' [11:52:46] Logged the message at https://wikitech.wikimedia.org/wiki/Release_Engineering/SAL [11:57:30] Project beta-scap-eqiad build #144645: 04FAILURE in 1 min 57 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144645/ [11:58:33] 10Browser-Tests-Infrastructure, 10MediaWiki-General-or-Unknown, 07JavaScript, 13Patch-For-Review, and 2 others: Port Selenium tests from Ruby to Node.js - https://phabricator.wikimedia.org/T139740#3067590 (10zeljkofilipin) [11:59:25] 10Browser-Tests-Infrastructure, 10MediaWiki-General-or-Unknown, 07JavaScript, 13Patch-For-Review, and 2 others: Port Selenium tests from Ruby to Node.js - https://phabricator.wikimedia.org/T139740#2441243 (10zeljkofilipin) [12:06:31] Project beta-scap-eqiad build #144646: 04STILL FAILING in 1 min 32 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144646/ [12:12:50] 06Release-Engineering-Team, 10Monitoring, 06Operations, 07Tracking, 07Wikimedia-Incident: Tracking: Monitoring and alerts for "business" metrics - https://phabricator.wikimedia.org/T140942#3067616 (10hashar) [12:16:31] Project beta-scap-eqiad build #144647: 04STILL FAILING in 1 min 36 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144647/ [12:28:31] Yippee, build fixed! [12:28:32] Project beta-scap-eqiad build #144648: 09FIXED in 3 min 37 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144648/ [12:47:41] 10Continuous-Integration-Infrastructure, 07Composer, 13Patch-For-Review: Upgrade integration/composer to 1.3.2 stable - https://phabricator.wikimedia.org/T125343#3067701 (10Paladox) Should we try upgrading to composer 1.3.2 now? [13:07:46] 10Continuous-Integration-Config, 10BlueSpice, 13Patch-For-Review: Enable unit tests on BlueSpice* repos - https://phabricator.wikimedia.org/T130811#3067735 (10Osnard) @Paladox What do I need to do to make `mwext-testextension-hhvm-jessie-non-voting` load BlueSpiceFoundation when testing any other BlueSpice*... [13:20:04] 10Continuous-Integration-Config, 10BlueSpice, 13Patch-For-Review: Enable unit tests on BlueSpice* repos - https://phabricator.wikimedia.org/T130811#3067775 (10Paladox) @Osnard Oh I did that in the integration/config repo in this https://phabricator.wikimedia.org/diffusion/CICF/browse/master/zuul/parameter_fu... [13:49:09] PROBLEM - Puppet run on buildlog is CRITICAL: CRITICAL: 100.00% of data above the critical threshold [0.0] [14:04:44] 10Continuous-Integration-Config, 10BlueSpice, 13Patch-For-Review: Enable unit tests on BlueSpice* repos - https://phabricator.wikimedia.org/T130811#3067811 (10Osnard) @Paladox Thank you! [14:13:43] (03PS1) 10Robert Vogel: Adding dependencies for current BlueSpice* repos [integration/config] - 10https://gerrit.wikimedia.org/r/340747 [14:14:14] 10Continuous-Integration-Config, 10BlueSpice, 13Patch-For-Review: Enable unit tests on BlueSpice* repos - https://phabricator.wikimedia.org/T130811#3067817 (10Osnard) I added some new repos: https://gerrit.wikimedia.org/r/340747 [14:26:39] (03PS1) 10Zfilipin: The gem requires Ruby version 2 [selenium] - 10https://gerrit.wikimedia.org/r/340748 (https://phabricator.wikimedia.org/T158074) [14:35:56] (03CR) 10Hashar: [C: 032] The gem requires Ruby version 2 [selenium] - 10https://gerrit.wikimedia.org/r/340748 (https://phabricator.wikimedia.org/T158074) (owner: 10Zfilipin) [14:37:10] (03Merged) 10jenkins-bot: The gem requires Ruby version 2 [selenium] - 10https://gerrit.wikimedia.org/r/340748 (https://phabricator.wikimedia.org/T158074) (owner: 10Zfilipin) [14:37:48] (03CR) 10jenkins-bot: The gem requires Ruby version 2 [selenium] - 10https://gerrit.wikimedia.org/r/340748 (https://phabricator.wikimedia.org/T158074) (owner: 10Zfilipin) [14:57:45] 10Deployment-Systems, 10Scap, 13Patch-For-Review: Update Debian Package for Scap3 - https://phabricator.wikimedia.org/T127762#3067863 (10fgiunchedi) 05Open>03Resolved Package is out [15:01:38] (03Abandoned) 10Hashar: Do not require specific versions of PHPCS [tools/codesniffer] - 10https://gerrit.wikimedia.org/r/333123 (owner: 10Jeroen De Dauw) [15:14:45] I think I need some help to debug an error jenkins :) [15:15:00] https://integration.wikimedia.org/ci/job/mediawiki-extensions-hhvm-jessie/7215/console [15:16:10] there are some compilation errors in core apparently, but looking at other build (in core) I don't this problem problem happening [15:16:31] ** I don't see this problem happening [15:17:15] errors are like: Use of undefined constant TS_MW - assumed 'TS_MW' in /home/jenkins/workspace/mediawiki-extensions-hhvm-jessie/src/includes/user/User.php on line 1154 [15:17:26] or: Fatal error: unknown class Wikimedia\Timestamp\ConvertibleTimestamp in /home/jenkins/workspace/mediawiki-extensions-hhvm-jessie/src/includes/MWTimestamp.php on line 32 [15:28:38] 06Release-Engineering-Team, 10Monitoring, 06Operations, 07Tracking, 07Wikimedia-Incident: Tracking: Monitoring and alerts for "business" metrics - https://phabricator.wikimedia.org/T140942#3067970 (10Peter) I've been trying out alerts for a while, let me write down a summary the coming days. [15:28:42] last one we had in CX as well [15:28:58] https://gerrit.wikimedia.org/r/313683 is the cuase [15:29:07] so likely missing composer update? [15:29:22] where is the class Wikimedia\Timestamp\ConvertibleTimestamp ? [15:29:24] dcausse: ^ [15:30:06] dcausse: 00:00:29.175 INFO:zuul.Cloner:Prepared mediawiki/vendor repo with branch es5 at commit c0a28023e01872190ab30ec7ec517b8334523096 [15:30:14] your change has been made against the es5 branch of whatever repo [15:30:28] and the job clones mediawiki/vendor @ es5 as well [15:30:37] I guess that branch might not have the proper set of dependencies [15:30:48] not sure why there is a need for an es5 branch in mediawiki/vendor though [15:45:08] Project selenium-MobileFrontend » chrome,beta,Linux,BrowserTests build #345: 04FAILURE in 23 min: https://integration.wikimedia.org/ci/job/selenium-MobileFrontend/BROWSER=chrome,MEDIAWIKI_ENVIRONMENT=beta,PLATFORM=Linux,label=BrowserTests/345/ [15:51:21] PROBLEM - puppet last run on contint1001 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [16:01:21] RECOVERY - puppet last run on contint1001 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [16:03:00] 10Continuous-Integration-Config, 06Operations, 13Patch-For-Review: Create a basic RSpec unit test for operations/puppet - https://phabricator.wikimedia.org/T78342#3068047 (10hashar) 05Open>03Resolved Bulk of the integration is done and there are spec being added to the repo. I wrote a guide on https://w... [16:03:09] 10Continuous-Integration-Config, 06Operations, 13Patch-For-Review: Create a basic RSpec unit test for operations/puppet - https://phabricator.wikimedia.org/T78342#3068049 (10hashar) 05Resolved>03Open [16:14:43] hashar: oh thanks! I'll upgrade vendor@es5, usually I get different errors (e.g. ooui required version X but version Y is installed) [16:15:57] vendor@es5 is needed because we upgrade the lib Elastica which is managed by vendor, and it would be incompatible with master [16:17:39] dcausse: makes sense :) [16:23:18] 10MediaWiki-Codesniffer: Split codesniffer repo into 2 (codesniffer & codesniffer-sniffs) - https://phabricator.wikimedia.org/T133011#3068097 (10Addshore) p:05Lowest>03Low [16:43:46] 10Browser-Tests-Infrastructure, 10MediaWiki-General-or-Unknown, 07JavaScript, 13Patch-For-Review, and 2 others: Port Selenium tests from Ruby to Node.js - https://phabricator.wikimedia.org/T139740#3068143 (10greg) [16:47:05] question about composer: what is the version I should use to update vendor? [16:48:05] I tried to merge vendor@master into a branch we maintain (vendor@es5) but I feel like I'm reverting some changes [16:48:18] e.g. the timestamp format [16:48:23] https://gerrit.wikimedia.org/r/#/c/340767/1/composer.lock [16:50:31] dcausse hi, composer 1.1.0+ [16:51:14] paladox: I run 1.1.3, but I'm not sure why the time format changed this time [16:51:31] Oh [16:51:32] Maybe try composer 1.3.2? [16:52:53] paladox: oh yes, seems to be due to https://gerrit.wikimedia.org/r/#/c/339599/ [16:53:06] composeroh [16:53:07] yep [16:53:49] thanks, will try again with 1.3.2 [16:54:02] Your welcome :) [16:54:57] RainbowSprinkles i might as well create another rest api to partially fix polygerrit on running prefixed urls :) [16:55:12] or i could use the existing /config/server/info one. [16:55:41] But this will require apache rewrite rules still [17:50:18] it looks like composer in jenkins is using 1.1.0, afaict the error we are getting is from: https://github.com/composer/composer/blob/1.1.0/src/Composer/Console/Application.php#L194 [17:50:46] the $io object not existing is a bug in composer, but the underlying problem seems to be that composer can't create a temp file? [17:51:53] it looks like this runs inside nodepool, so i'm not able to log into the machines that run the code and debug [17:54:15] ebernhardson i think that is fix in composer 1.1.1 [17:54:16] see https://github.com/composer/composer/commit/360cb4ac2af350c8b96b2fd56b67ef9d5589836a [17:54:38] paladox: right, but i have no control over what version of composer the jenkins job wants to run [17:54:50] ebernhardson we have a repo [17:54:54] that we can update [17:55:32] https://gerrit.wikimedia.org/r/#/admin/projects/integration/composer [17:56:05] hmm, hashar isn't around to say why he chose 1.1.0 vs say, 1.1.3 [17:56:07] i will create the patch to update it now [17:56:46] tim recently updated mediawiki/vendor to use 1.3.2 [17:56:54] or at least, regenerated it with 1.3.2 [17:57:01] s/tim/legoktm/ [17:58:29] (03PS1) 10Paladox: Update composer to 1.1.3 [integration/composer] - 10https://gerrit.wikimedia.org/r/340780 (https://phabricator.wikimedia.org/T125343) [17:58:37] ebernhardson ^^ [18:00:07] well, lets see what happens i suppose. does that have to be deployed somehow after merging? [18:01:31] Yep [18:01:45] hashar did "!log upgrading composer on permanent slaves for T125343 : salt -v '*slave*' cmd.run 'cd /srv/deployment/integration/composer && git pull'" [18:01:46] T125343: Upgrade integration/composer to 1.3.2 stable - https://phabricator.wikimedia.org/T125343 [18:01:53] ebernhardson ^^ [18:03:35] paladox: does it mean that composer 1.3.2 is already deployed on jenkins slaves? [18:03:50] Nope, hashar is doing it in stages i think [18:04:07] to try and prevent causing lots of problems. [18:04:10] ok so we just have to wait? [18:04:14] Yep [18:04:16] ok, thanks [18:04:19] We have a task for upgrading composer [18:04:25] https://phabricator.wikimedia.org/T125343 [18:04:30] dcausee ^^ [18:04:34] paladox: thanks [18:04:37] woops wrong name dcausse [18:04:42] your welcome :) [18:05:58] 10Continuous-Integration-Infrastructure, 07Composer, 13Patch-For-Review: Upgrade integration/composer to 1.3.2 stable - https://phabricator.wikimedia.org/T125343#1985014 (10EBernhardson) It looks like the update to composer 1.1.0 (perhaps only tangentially related?) has broken all jenkins runs to the CirrusS... [18:06:49] dcausse per hashar comment on https://gerrit.wikimedia.org/r/#/c/339645/ "I am being conservative and just do a 1.1.0-RC..1.1.0 bump so we bring in less changes. My hope is that this way the change has less surface to fail. My main goal is to support adding 'extra' settings using composer config for T125343 [18:06:49] If that works all fine, I guess we can go with another change that further bumps composer to 1.3.2." [18:06:49] T125343: Upgrade integration/composer to 1.3.2 stable - https://phabricator.wikimedia.org/T125343 [18:07:22] 10Continuous-Integration-Infrastructure, 07Composer, 13Patch-For-Review: Upgrade integration/composer to 1.3.2 stable - https://phabricator.wikimedia.org/T125343#3068471 (10Paladox) ^^ that should be fixed in https://gerrit.wikimedia.org/r/340780 :) [18:07:58] 10Continuous-Integration-Infrastructure, 07Composer, 13Patch-For-Review: Upgrade integration/composer to 1.3.2 stable - https://phabricator.wikimedia.org/T125343#3068472 (10EBernhardson) Additionally it looks like not only CirrusSearch, perhaps all jobs using mwext-php60-phan-jessie? See also https://gerrit.... [18:08:57] ebernhardson or dcausse could you create a task for the broken phan test, so we ajust priority on fixing that please? [18:09:05] (03CR) 10DCausse: [C: 031] Update composer to 1.1.3 [integration/composer] - 10https://gerrit.wikimedia.org/r/340780 (https://phabricator.wikimedia.org/T125343) (owner: 10Paladox) [18:09:15] paladox: sure [18:09:31] we can merge it, but you have to find someone with appropriate salt access to deploy [18:09:32] Thanks :) [18:10:22] Reedy do you have access or twentyafterfour or thcipriani ^^? [18:12:47] 10Continuous-Integration-Infrastructure: Composer 1.1.0 is causing failures on phan jobs - https://phabricator.wikimedia.org/T159469#3068481 (10dcausse) [18:13:25] 10Continuous-Integration-Infrastructure: Composer 1.1.0 is causing failures on phan jobs - https://phabricator.wikimedia.org/T159469#3068498 (10Paladox) p:05Triage>03Unbreak! [18:13:59] 10Continuous-Integration-Infrastructure: Composer 1.1.0 is causing failures on phan jobs - https://phabricator.wikimedia.org/T159469#3068502 (10Paladox) [18:14:01] 10Continuous-Integration-Infrastructure, 07Composer, 13Patch-For-Review: Upgrade integration/composer to 1.3.2 stable - https://phabricator.wikimedia.org/T125343#3068501 (10Paladox) [18:15:19] 10Continuous-Integration-Infrastructure, 07Composer: Composer 1.1.0 is causing failures on phan jobs - https://phabricator.wikimedia.org/T159469#3068481 (10Paladox) [18:17:26] (03CR) 10Paladox: "This https://github.com/composer/composer/commit/360cb4ac2af350c8b96b2fd56b67ef9d5589836a is the fix we want." [integration/composer] - 10https://gerrit.wikimedia.org/r/340780 (https://phabricator.wikimedia.org/T125343) (owner: 10Paladox) [18:22:41] 10MediaWiki-Codesniffer, 06Community-Tech, 13Patch-For-Review: Undefined index: scope_opener in MediaWiki/Sniffs/Usage/ExtendClassUsageSniff.php - https://phabricator.wikimedia.org/T154731#3068555 (10DannyH) [18:24:41] (03CR) 10EBernhardson: [C: 032] Update composer to 1.1.3 [integration/composer] - 10https://gerrit.wikimedia.org/r/340780 (https://phabricator.wikimedia.org/T125343) (owner: 10Paladox) [18:24:52] (03Merged) 10jenkins-bot: Update composer to 1.1.3 [integration/composer] - 10https://gerrit.wikimedia.org/r/340780 (https://phabricator.wikimedia.org/T125343) (owner: 10Paladox) [18:25:00] thanks ^^ [18:25:55] godog ran the salt command, will see if it fixed the problem [18:26:02] 10Continuous-Integration-Infrastructure, 07Composer: Composer 1.1.0 is causing failures on phan jobs - https://phabricator.wikimedia.org/T159469#3068566 (10Paladox) Should be fixed in https://gerrit.wikimedia.org/r/#/c/340780/ [18:26:02] ok thanks [18:26:08] !log integration update composer on '*slave*' [18:26:13] Logged the message at https://wikitech.wikimedia.org/wiki/Release_Engineering/SAL [18:26:30] dangit I should have cc'd the task [18:31:34] Still fails with https://integration.wikimedia.org/ci/job/mwext-php70-phan-jessie/531/console [18:31:44] ebernhardson dcausse ^^ [18:31:51] uhhh. catching up. In order for the nodepool slaves to get this change I think we have to rebuild the nodepool image. The salt command will just deploy to permanent nodes. [18:32:19] :( [18:32:45] oh [18:39:54] the nodepool image rebuild happens once per day, ftr [18:40:00] (03PS1) 10Gergő Tisza: Add EddieGP to the CI whitelist [integration/config] - 10https://gerrit.wikimedia.org/r/340790 [18:41:14] Yep i think at around 2pm utc time? [18:41:48] (03CR) 10Paladox: [C: 031] Add EddieGP to the CI whitelist [integration/config] - 10https://gerrit.wikimedia.org/r/340790 (owner: 10Gergő Tisza) [18:43:24] tgr: Thanks. [18:44:39] (03PS1) 10Paladox: Update composer ti 1.3.2 [integration/composer] - 10https://gerrit.wikimedia.org/r/340791 (https://phabricator.wikimedia.org/T125343) [18:46:36] (03PS2) 10Paladox: Update composer to 1.3.2 [integration/composer] - 10https://gerrit.wikimedia.org/r/340791 (https://phabricator.wikimedia.org/T125343) [18:47:01] (03CR) 10EddieGP: [C: 031] Add EddieGP to the CI whitelist [integration/config] - 10https://gerrit.wikimedia.org/r/340790 (owner: 10Gergő Tisza) [18:53:08] so I'm looking at the scrollback here and I'm catching up slowly (I haven't been in the loop on this) we upgraded to composer 1.1.0 this morning for...some reason(?) and that broke things, so then we wanted to upgrade again but nodepool instances haven't been upgraded. I still don't know why we upgraded in the first place? Is it reasonable to revert that or will that break everything? [18:53:29] * thcipriani digs in phab some more [18:56:12] so it seems like we upgraded due to: https://phabricator.wikimedia.org/T158674#3067306 [18:56:31] it seems like if the upgrade is causing problems, we should just roll it back. [18:58:20] composer 1.1.1 will most likly fix the problem per erbernhardson finding on the tmp bug. [18:58:37] thcipriani: the part the broke in composer was just a bad release, the 1.1.0 release contained a fatal error. Rolling back could work, but it seems sane to use the most recent point release and test with 1.1.3 rather than 1.1.0 [18:59:33] ah, ok, well let me try to rebuild the nodepool image with what is merged now and see if that fixes things [19:00:23] (although this will be a first for me, so bear with me) [19:00:52] 10Continuous-Integration-Infrastructure, 07Composer: Upgrade of composer to v1.1.0 breaks some builds - https://phabricator.wikimedia.org/T159431#3068669 (10Ricordisamoa) [19:02:06] thanks [19:15:11] !log running: nodepool image-update wmflabs-eqiad snapshot-ci-jessie to manually update the ci-jessie snapshot for nodepool [19:15:14] Logged the message at https://wikitech.wikimedia.org/wiki/Release_Engineering/SAL [19:17:31] 10Beta-Cluster-Infrastructure, 10Cognate, 10MediaWiki-extensions-InterwikiSorting, 13Patch-For-Review, 15User-Addshore: Create beta hewiktionary for testing InterwikiSorting & Cognate - https://phabricator.wikimedia.org/T158628#3068701 (10Addshore) It looks like this now exists! https://he.wiktionary.be... [19:32:20] !log snapshot-ci-jessie updated for nodepool [19:32:25] Logged the message at https://wikitech.wikimedia.org/wiki/Release_Engineering/SAL [19:36:15] OK, I'm not sure which images are built from which snapshots, but as soon as the old images clear out we'll start seeing ci-jessie images being built from the new snapshot [19:36:37] which should hopefully fix the problem in T159469 [19:36:38] T159469: Composer 1.1.0 is causing failures on phan jobs - https://phabricator.wikimedia.org/T159469 [19:37:32] Thanks :) [19:37:33] ebernhardson dcausse ^^ [19:39:45] its working [19:39:47] https://integration.wikimedia.org/ci/job/mwext-php70-phan-jessie/538/console [19:39:52] thcipriani ^^ :) [19:40:05] not fataling as fast as did before [19:40:14] ebernhardson dcausse ^^ [19:40:17] nice :) [19:41:44] paladox: thanks for helping me work out what was happening here [19:41:48] 10Continuous-Integration-Infrastructure, 07Composer, 13Patch-For-Review: Upgrade integration/composer to 1.3.2 stable - https://phabricator.wikimedia.org/T125343#3068769 (10Paladox) [19:41:51] 10Continuous-Integration-Infrastructure, 07Composer: Composer 1.1.0 is causing failures on phan jobs - https://phabricator.wikimedia.org/T159469#3068766 (10Paladox) 05Open>03Resolved a:03Paladox Works now see https://integration.wikimedia.org/ci/job/mwext-php70-phan-jessie/538/console please. [19:41:52] Yep and your welcome :) [19:42:00] ebernhardson: dcausse thanks for bearing with me while I figured out how to update snapshots :\ [19:42:13] also thanks for updating the snapshot [19:42:23] werd :) [19:42:26] hmm, indeed that looks to have fixed the problem with composer failing. wonder what is triggering the failure now since it sees '0 unique warnings and 0 failures' [19:45:19] hey, need help with scap deploy: I tried to deploy tilerator, it failed because I frogot to update submodule, now all attempts at scap deploy just no-op out in 3 seconds [19:46:14] MaxSem: try a scap deploy --force [19:46:36] Another option: roll back tin to prior-deployed version, deploy that sha1 again? Then re-try? [19:46:42] (if --force doesn't work) [19:46:50] --force didn't work [19:47:40] Meta thought: checking git repo on tin for sanity (uncommitted files, modified files, out-of-date submodules) is probably a decent idea before deploy [19:47:48] At least warn (are you sure these things are ok? y/n) [19:48:35] speaking of uncommitted files, I see scap/log [19:48:56] scap thinks edb97c5224d9ae537e000bdb054c002979b90fa8 is deployed, is that not the case [19:48:58] ? [19:49:21] MaxSem: Yes, those can be added to .gitignore, if you're feeling bothered by them [19:49:25] No need to ever commit [19:49:34] no, it failed deploying to canary so I aborted [19:49:34] (generally, let's add that to /etc/gitconfig on tin/mira) [19:50:41] MaxSem: you seem to be in a detatched head on tin [19:51:02] I tried deploying previous version, as recommended [19:51:32] wohoo [19:51:32] master now [19:51:37] i figure out a fix for polygerrit [19:51:49] well at least it will fix it for us [19:51:50] :) [19:51:57] RainbowSprinkles ^^ [19:54:25] aaaaaaaa [19:54:29] MaxSem: ok, so, you're trying to deploy edb97c5224d9ae537e000bdb054c002979b90fa8 [19:54:44] yes [19:54:52] scap thinks 0fe5a1d159453cad283596baed728f1e643a3d7d is currently deployed [19:55:26] actually scap now show edb97c5224d9ae537e000bdb054c002979b90fa8 as deployed [19:56:03] MaxSem: what is not working? Is the service down? [19:56:18] git log on maps-test2001 shows 0fe5a1d159453cad283596baed728f1e643a3d7d [19:56:26] Project beta-scap-eqiad build #144692: 04FAILURE in 1 min 35 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144692/ [19:56:56] I see HEAD detached at edb97c5 [19:57:01] MaxSem: ^ [19:57:06] on maps-test2001 [19:57:10] the service is up and running what it was running before my attempts [19:57:28] can you re-cd to /srv/deployment/tilerator/deploy? [19:57:38] we move that directory as part of deployment [19:57:47] you may, somehow, be seeing old information [19:57:57] Project beta-scap-eqiad build #144693: 04STILL FAILING in 1 min 18 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144693/ [19:58:12] RainbowSprinkles my fix https://gerrit-review.googlesource.com/#/c/99004/ [19:58:16] ahaha [19:58:21] now see my commit [19:58:30] will require us to use apache rewrite rules for moving bower_components from / to /r/ [19:58:32] magic mv's on linux confuse me all the time [19:58:40] MaxSem: all good then? [19:58:44] confuse my ls -al's all the time, that is :) [19:58:59] yep, just need to restart [19:59:13] coolio :) [19:59:23] thanks \m/ [20:05:58] paladox: thanks for fixing the composer stuff [20:06:22] Project beta-scap-eqiad build #144694: 04STILL FAILING in 1 min 18 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144694/ [20:16:30] Project beta-scap-eqiad build #144695: 04STILL FAILING in 1 min 30 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144695/ [20:16:58] blerg. This host key thing for scap in beta sure is mad. [20:17:10] * thcipriani shuts it up for now [20:20:15] legoktm your welcome :) [20:26:17] Project beta-scap-eqiad build #144696: 04STILL FAILING in 1 min 18 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144696/ [20:26:36] ^^ 20:26:16 sudo -u mwdeploy -n -- /usr/bin/rsync -l deployment-tin.deployment-prep.eqiad.wmflabs::common/wikiversions*.{json,php} /srv/mediawiki on deployment-tin.deployment-prep.eqiad.wmflabs returned [255]: Host key verification failed. [20:26:37] 20:26:16 [20:27:08] hrm, I thought I just accepted those keys [20:27:17] puppet is doing something to clean them out [20:27:22] and that is frustrating. [20:34:58] thcipriani: I filled a bug for that [20:35:12] something like /etc/ssh/known_hosts get erased by puppet somehow [20:35:24] the host keys are supposedly collected to build that file [20:35:58] https://phabricator.wikimedia.org/T159332 [20:36:12] Project beta-scap-eqiad build #144697: 04STILL FAILING in 1 min 22 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144697/ [20:41:57] 10Beta-Cluster-Infrastructure, 06Release-Engineering-Team: Beta cluster scap job ( beta-scap-eqiad ) fails due to puppet erasing /etc/ssh/ssh_known_hosts - https://phabricator.wikimedia.org/T159332#3068911 (10hashar) $ md5sum <( echo "# This file is managed by puppet" ) 3e04e1a906c0d2df1d4eea34e4bd0f4e /dev/f... [20:47:11] Yippee, build fixed! [20:47:12] Project beta-scap-eqiad build #144698: 09FIXED in 2 min 18 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144698/ [20:47:54] !log deployment-prep: restarted apache/puppet master. Maybe that will fix ssh_known_hosts being emptied from time to time T159332 [20:47:58] Logged the message at https://wikitech.wikimedia.org/wiki/Release_Engineering/SAL [20:47:59] T159332: Beta cluster scap job ( beta-scap-eqiad ) fails due to puppet erasing /etc/ssh/ssh_known_hosts - https://phabricator.wikimedia.org/T159332 [20:49:26] PROBLEM - Puppet run on deployment-tin is CRITICAL: CRITICAL: 33.33% of data above the critical threshold [0.0] [20:50:06] PROBLEM - Puppet run on deployment-phab02 is CRITICAL: CRITICAL: 44.44% of data above the critical threshold [0.0] [20:50:30] (03PS2) 10Hashar: Add EddieGP to the CI whitelist [integration/config] - 10https://gerrit.wikimedia.org/r/340790 (owner: 10Gergő Tisza) [20:51:00] (03CR) 10Hashar: [C: 032] Add EddieGP to the CI whitelist [integration/config] - 10https://gerrit.wikimedia.org/r/340790 (owner: 10Gergő Tisza) [20:51:48] (03Merged) 10jenkins-bot: Add EddieGP to the CI whitelist [integration/config] - 10https://gerrit.wikimedia.org/r/340790 (owner: 10Gergő Tisza) [20:52:10] PROBLEM - Puppet run on deployment-jobrunner02 is CRITICAL: CRITICAL: 55.56% of data above the critical threshold [0.0] [20:52:25] (03CR) 10Hashar: "Deploying that on CI and we will see what happens" [integration/composer] - 10https://gerrit.wikimedia.org/r/340780 (https://phabricator.wikimedia.org/T125343) (owner: 10Paladox) [20:52:52] hashar ^^ i think that was deployed [20:52:56] and fixed the problem :) [20:53:10] godog deployed it and thcipriani updated the nodepool image [20:53:15] ohh nice [20:53:31] yep ::) [20:53:36] operations/mediawiki-config exploded completely [20:53:39] but that was unrelate [20:53:40] d [20:53:47] due to another lame bug [20:54:20] Oh which bug is that? [20:54:30] I think the 1.1.x release had a fix [20:54:36] for using -d [20:54:53] I guess we can do 1.3.2 tomorrow :] [20:55:09] Yep :) :) [20:55:21] \O/ [20:56:47] That will include some performance improvements to composer i think [20:56:51] it uses cache [21:05:27] 10Continuous-Integration-Infrastructure, 07Composer: Upgrade of composer to v1.1.0 breaks some builds - https://phabricator.wikimedia.org/T159431#3068977 (10hashar) From T125343#3068454 and below, that also broke mwext-php70-phan-jessie . Got fixed by bumping to 1.1.3 [21:09:26] RECOVERY - Puppet run on deployment-tin is OK: OK: Less than 1.00% above the threshold [0.0] [21:12:24] 10Continuous-Integration-Config, 06Release-Engineering-Team, 06Discovery, 06Discovery-Analysis: Add CI to all wikimedia/discovery repositories that are active - https://phabricator.wikimedia.org/T153856#3069032 (10debt) p:05Triage>03Normal [21:25:05] RECOVERY - Puppet run on deployment-phab02 is OK: OK: Less than 1.00% above the threshold [0.0] [21:27:09] RECOVERY - Puppet run on deployment-jobrunner02 is OK: OK: Less than 1.00% above the threshold [0.0] [21:56:33] Project beta-scap-eqiad build #144704: 04FAILURE in 1 min 29 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144704/ [21:59:06] hashar ^^ [22:07:05] Project beta-scap-eqiad build #144705: 04STILL FAILING in 1 min 58 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144705/ [22:13:41] 10Gerrit, 07Upstream: Gerrit Internal Server Error when trying to cherry-pick patch from master to master - https://phabricator.wikimedia.org/T149878#3069214 (10Paladox) 05Open>03Resolved This should now work. Please re open if the problem still happens. [22:15:18] 10Gerrit, 07Upstream: In changeset view, clicking the "Owner" name does not display list of their changesets but of unrelated other user - https://phabricator.wikimedia.org/T146361#3069223 (10Paladox) Polygerrit uses the email by default now. Polygerrit will be exposed in gerrit 2.14. [22:16:22] paladox: If we use polygerrit in 2.14 it's going to be opt-in only. There's too much missing stuff to make it default [22:16:38] Yes, i wouldent want it default either [22:16:49] Too much is missing from it :) [22:17:06] Project beta-scap-eqiad build #144706: 04STILL FAILING in 2 min 1 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144706/ [22:17:08] it's broken for us anyways. Though i really do hope upstream fix it in time for the 2.14 cut [22:17:13] RainbowSprinkles ^^ [22:17:34] If not, we can just leave it off until they fix it. [22:17:42] Better what works (even if ugly) than broken [22:17:56] 10Gerrit, 07Browser-Support-Internet-Explorer: Internet Explorer 8 cannot display gerrit patch set with @/at sign in search result - https://phabricator.wikimedia.org/T52818#3069227 (10Paladox) 05Open>03Resolved Closing as resolved as internet explorer 8 is unsupported by microsoft. You can use google chro... [22:18:03] yep [22:18:50] RainbowSprinkles I kind of figured out a fix for it, but it dosen't load properly. What they should do is use polymer-gwt instead. [22:19:32] I can't imagine it's a hard fix for them, but they probably don't care since google runs it in docroot :) [22:19:37] (care much) [22:19:38] :)) [22:20:23] 10Gerrit: Improve error message when viewing draft - https://phabricator.wikimedia.org/T49853#3069241 (10Paladox) 05Open>03declined Declining as upstream are removing support for drafts and replacing it with private edits. [22:20:34] (and really, you guys got this far without testing that??) [22:20:43] lol [22:21:07] RainbowSprinkles i filled two bug reports about this forgetting my first one was merged into another one. [22:21:19] https://bugs.chromium.org/p/gerrit/issues/detail?id=3795 [22:22:31] They suggested to do [22:22:33] "As we have soy available now, how about rendering polygerrit 'index.html' with soy to adopt to [22:22:33] [22:22:33] * css/js path with or without polygerrit_ui prefix [22:22:33] * canonical url/base context path" [22:22:41] in agust 2016 [22:22:46] it never happen. [22:22:57] That's lame that they'd expect third parties to work around it [22:23:04] They should just fix it to stop assuming things [22:23:10] yep [22:23:31] They want to turn polygerrit on by default next week [22:23:32] https://groups.google.com/forum/#!topic/repo-discuss/9rhEDC6GxoY [22:23:37] I *could* work around it possibly by rewriting *old* docroot stuff (like extension-list or whatever) prior to proxying the rest, but I could see that being a pain too [22:23:58] Yes a pain :), though rewrites are helping a bit for me [22:24:10] That *might* be nicer/easier than rewriting the polygerrit stuff [22:24:17] (rewrite our junk, not theirs is what I mean) [22:24:18] Yep [22:24:21] lol [22:24:22] i did get it working at on point, though it was rather broken. [22:24:35] Moving away from /r/ will break links too [22:24:39] So we'll want to rewrite those too [22:24:43] Srsly, they should just fix it [22:24:46] Yes [22:25:02] I guess we keep poking upstream may give them so more priority to the thing [22:25:17] polygerrit will never be able to be the default ui if they carn't fix this bug. [22:26:43] They have 306 bugs open with component:PolyGerrit [22:26:49] How on earth do they think that's ready for prime-time? [22:27:36] lol [22:28:09] There's always the polymer-gwt thing they could use if they really want polymer. It looks nice when going to polymer-gwt. [22:28:15] Yippee, build fixed! [22:28:15] would probaly reduce alot of tasks [22:28:15] Project beta-scap-eqiad build #144707: 09FIXED in 3 min 5 sec: https://integration.wikimedia.org/ci/job/beta-scap-eqiad/144707/ [22:29:13] paladox: Maybe. And don't get me wrong, it's certainly moving in the right direction long-term. But we can't in good faith recommend *anyone* use it yet on our end. It's broken enough to make people be unproductive :( [22:29:47] Yep, I think that they only test it on the gerrit-review site [22:29:56] and never thing about what other users might do. [22:36:21] RainbowSprinkles i did file https://groups.google.com/forum/#!topic/repo-discuss/20x95V-FNFo and havent got a response [22:36:50] Eh, let's just drop it for 2.15 [22:36:56] And assume it won't be ok til 2.16 [22:37:07] They aren't going to rush a fix I don't think, considering their response thus far [22:37:11] lolololololololololol [22:37:32] Yes, google probaly needs to give them more money [23:21:36] Hey, how often does the CI config get updated out of the integration/config repository? Is there a automatic/recurring process or must one schedule this anywhere? [23:23:31] It is done nearly every day [23:23:32] hashar normaly does it [23:23:36] except from the weekends [23:24:36] Okay, then I'll just wait for it ;) [23:24:47] ok [23:27:31] RainbowSprinkles i do like the polygerrit diffs [23:27:33] it looks 100% better then gwt. See http://gerrit-new.wmflabs.org/c/36/1/project.config#77 [23:27:49] + loads faster according to them. [23:32:58] 10Gerrit: Gerrit needs a very wide screen or has big horizontal scroll - https://phabricator.wikimedia.org/T38471#3069507 (10Paladox) I think we can close this as declined as polygerrit will be the new way to go ui wise once it is all ready. [23:36:28] RainbowSprinkles ah [23:36:34] i have an idea for polygerrit [23:36:48] i got it working locally with apache rewrites and no changes to gerrits core [23:37:09] It will not be perfect. These rewrites will not break gwt either so it will be safe [23:39:06] But it at least works, i can view settings, view a diff. Just that some things may break that a non prefixed url will not have.] [23:45:08] RainbowSprinkles heres the rewrites https://gerrit.wikimedia.org/r/#/c/340900/ :) [23:54:41] Should work [23:55:09] Yep [23:56:37] RainbowSprinkles the only problem i found is users will not be able to Write comments through poly gerrit or rebase or cherry-pick Which i think it is acceptible at the momement as we can shows polygerrit as a test for users to submit feedback upstream. Users can also use the footer to switch back to old gerrit ui [23:57:03] Heh, see what I said earlier about useless :p [23:57:09] No comments, no rebasing, no cherry picking [23:57:09] Yep lol [23:57:12] There goes swat [23:57:16] lol [23:57:31] Comments still work on gwt [23:58:05] I get this [23:58:06] Server error: Expected JSON object [23:58:13] so i must have miss some where. [23:59:33] where = rewrites. Ie maybe /config/server/*