Change Details

[To be refined] To be able to formulate our Hypothesis, we need some initial data on the topic to define the problem and the scope. As we've discussed in our last team meeting, we're going to focus on the CI jobs running the browser tests, specifically the Core tests and the Gated Extensions CI jobs (called **target jobs** going forward), with the primary focus on the Gated Extensions jobs. Preliminary data that we've collected so far: > We're running multiple jobs that execute the gated extensions tests (because we run them against different PHP versions), so there are two relevant jobs: 1. [[ https://releng-data.wmcloud.org/-/dashboards/jenkins?job_name=quibble-with-gated-extensions-selenium-php83&date_start=2025-10-01 | PHP83 ]] job_id = 751 2. [[ https://releng-data.wmcloud.org/-/dashboards/jenkins?job_name=quibble-with-gated-extensions-selenium-php81&date_start=2025-10-01 | PHP81 ]] job_id = 221 > The relevant dashboard with lots of statistical data is [[ https://releng-data.wmcloud.org/-/dashboards/jenkins?date_start=2025-10-01&date_end=&job_name=&repo_name=mediawiki%2Fcore&host_name= | here ]] > The median run time for gated extensions tests is around 21 minutes > We can either use gerrit or the same [[ https://releng-data.wmcloud.org/-/dashboards/jenkins?date_start=2025-10-01&date_end=&job_name=&repo_name=mediawiki%2Fcore&host_name= | dashboard ]] mentioned above to show the second slowest job The data we're looking for: 1. How long each of the **target jobs** takes (we need a screenshot with average, median, p75, p90, p95, p99). Ideally, in the case of Gated Extensions, we need data for both versions of PHP separately and then aggregated 2. What is the second slowest job that runs in parallel with the **target jobs** (again, a similar screenshot) in mediawiki/core? 3. What is the daily median runtime of each of the **target jobs**? AC: - We have an artifact (e.g. Google Doc) that answers the questions above and contains the screenshots - The document explains why we have two browser test steps per job with a different number of projects (68 vs 67)

[To be refined] To be able to formulate our Hypothesis, we need some initial data on the topic to define the problem and the scope. As we've discussed in our last team meeting, we're going to focus on the CI jobs running the browser tests, specifically the Core tests and the Gated Extensions CI jobs (called **target jobs** going forward), with the primary focus on the Gated Extensions jobs. Preliminary data that we've collected so far: > We're running multiple jobs that execute the gated extensions tests (because we run them against different PHP versions), so there are two relevant jobs: 1. [[ https://releng-data.wmcloud.org/-/dashboards/jenkins?job_name=quibble-with-gated-extensions-selenium-php83&date_start=2025-10-01 | PHP83 ]] job_id = 751 2. [[ https://releng-data.wmcloud.org/-/dashboards/jenkins?job_name=quibble-with-gated-extensions-selenium-php81&date_start=2025-10-01 | PHP81 ]] job_id = 221 > The relevant dashboard with lots of statistical data is [[ https://releng-data.wmcloud.org/-/dashboards/jenkins?date_start=2025-10-01&date_end=&job_name=&repo_name=mediawiki%2Fcore&host_name= | here ]] > The median run time for gated extensions tests is around 21 minutes > We can either use gerrit or the same [[ https://releng-data.wmcloud.org/-/dashboards/jenkins?date_start=2025-10-01&date_end=&job_name=&repo_name=mediawiki%2Fcore&host_name= | dashboard ]] mentioned above to show the second slowest job The data we're looking for: 1. How long each of the **target jobs** takes (we need a screenshot with average, median, p75, p90, p95, p99). Ideally, in the case of Gated Extensions, we need data for both versions of PHP separately and then aggregated 2. What is the second slowest job that runs in parallel with the **target jobs** (again, a similar screenshot) in mediawiki/core? 3. What is the daily median runtime of each of the **target jobs**? AC: [] We have an artifact (e.g. [[ https://docs.google.com/document/d/10dZokf8qex9sjTrM5Lr5buUKeCOziADazaopavLSiOo/edit?usp=sharing | Google Doc ]]) that answers the questions above and contains the screenshots [] The document explains why we have two browser test steps per job with a different number of projects (68 vs 67)

[To be refined] To be able to formulate our Hypothesis, we need some initial data on the topic to define the problem and the scope. As we've discussed in our last team meeting, we're going to focus on the CI jobs running the browser tests, specifically the Core tests and the Gated Extensions CI jobs (called **target jobs** going forward), with the primary focus on the Gated Extensions jobs. Preliminary data that we've collected so far: > We're running multiple jobs that execute the gated extensions tests (because we run them against different PHP versions), so there are two relevant jobs: 1. [[ https://releng-data.wmcloud.org/-/dashboards/jenkins?job_name=quibble-with-gated-extensions-selenium-php83&date_start=2025-10-01 | PHP83 ]] job_id = 751 2. [[ https://releng-data.wmcloud.org/-/dashboards/jenkins?job_name=quibble-with-gated-extensions-selenium-php81&date_start=2025-10-01 | PHP81 ]] job_id = 221 > The relevant dashboard with lots of statistical data is [[ https://releng-data.wmcloud.org/-/dashboards/jenkins?date_start=2025-10-01&date_end=&job_name=&repo_name=mediawiki%2Fcore&host_name= | here ]] > The median run time for gated extensions tests is around 21 minutes > We can either use gerrit or the same [[ https://releng-data.wmcloud.org/-/dashboards/jenkins?date_start=2025-10-01&date_end=&job_name=&repo_name=mediawiki%2Fcore&host_name= | dashboard ]] mentioned above to show the second slowest job The data we're looking for: 1. How long each of the **target jobs** takes (we need a screenshot with average, median, p75, p90, p95, p99). Ideally, in the case of Gated Extensions, we need data for both versions of PHP separately and then aggregated 2. What is the second slowest job that runs in parallel with the **target jobs** (again, a similar screenshot) in mediawiki/core? 3. What is the daily median runtime of each of the **target jobs**? AC: -[] We have an artifact (e.g. [[ https://docs.google.com/document/d/10dZokf8qex9sjTrM5Lr5buUKeCOziADazaopavLSiOo/edit?usp=sharing | Google Doc ]]) that answers the questions above and contains the screenshots -[] The document explains why we have two browser test steps per job with a different number of projects (68 vs 67)