From 49a1b9d9f3b2cea66d5babd77a96dcc00469fba7 Mon Sep 17 00:00:00 2001 From: Erik Bernhardson Date: Thu, 30 Jun 2016 17:05:16 -0700 Subject: [PATCH] Remove Profiler specific code from fileOpPerfTest This code was referencing classes that no longer exist, so it was removed. Profiling can still be accomplished the same way normal maint scripts are profiled, by populating StartProfiler.php and passing '--profiler ProfilerOutputText', or something similar, on the maint script command line. Change-Id: Ie037f6b224ec361c86b86369e2a4fff641908053 --- maintenance/fileOpPerfTest.php | 5 ----- 1 file changed, 5 deletions(-) diff --git a/maintenance/fileOpPerfTest.php b/maintenance/fileOpPerfTest.php index 92547ca786..4b6c619414 100644 --- a/maintenance/fileOpPerfTest.php +++ b/maintenance/fileOpPerfTest.php @@ -42,8 +42,6 @@ class TestFileOpPerformance extends Maintenance { } public function execute() { - Profiler::setInstance( new ProfilerSimpleText( [] ) ); // clear - $backend = FileBackendGroup::singleton()->get( $this->getOption( 'b1' ) ); $this->doPerfTest( $backend ); @@ -51,9 +49,6 @@ class TestFileOpPerformance extends Maintenance { $backend = FileBackendGroup::singleton()->get( $this->getOption( 'b2' ) ); $this->doPerfTest( $backend ); } - - Profiler::instance()->setTemplated( true ); - // NOTE: as of MW1.21, $profiler->logData() is called implicitly by doMaintenance.php. } protected function doPerfTest( FileBackend $backend ) { -- 2.20.1