[FTR] Track process duration + test stats in run-end #238397
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dgieselaar
added
release_note:skip
Contributor
💔 Build Failed
Failed CI StepsMetrics [docs]Public APIs missing comments
Historycc @dgieselaar |
dgieselaar
added
backport:all-open
Contributor
|
Starting backport for target branches: 8.18, 8.19, 9.1, 9.2 https://github.com/elastic/kibana/actions/runs/18500172047 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Oct 14, 2025
Currently we only measure the root suite duration, which does not include the time to start Elasticsearch, Kibana (which are started before Mocha runs) and the docker containers (which are in the `beforeTests` lifecycle). With this change, we start tracking A) total process duration which will capture these phases, B) test stats, so we can see the distribution of test counts across configs and the relation between test counts and process/test run duration (cherry picked from commit 086c290)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Oct 14, 2025
Currently we only measure the root suite duration, which does not include the time to start Elasticsearch, Kibana (which are started before Mocha runs) and the docker containers (which are in the `beforeTests` lifecycle). With this change, we start tracking A) total process duration which will capture these phases, B) test stats, so we can see the distribution of test counts across configs and the relation between test counts and process/test run duration (cherry picked from commit 086c290)
Contributor
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Oct 14, 2025
…238923) # Backport This will backport the following commits from `main` to `9.1`: - [[FTR] Track process duration + test stats in run-end (#238397)](#238397) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dario Gieselaar","email":"dario.gieselaar@elastic.co"},"sourceCommit":{"committedDate":"2025-10-14T14:36:17Z","message":"[FTR] Track process duration + test stats in run-end (#238397)\n\nCurrently we only measure the root suite duration, which does not\ninclude the time to start Elasticsearch, Kibana (which are started\nbefore Mocha runs) and the docker containers (which are in the\n`beforeTests` lifecycle).\n\nWith this change, we start tracking A) total process duration which will\ncapture these phases, B) test stats, so we can see the distribution of\ntest counts across configs and the relation between test counts and\nprocess/test run duration","sha":"086c2900f274de0239dccb82595b93a883fa946b","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.3.0"],"title":"[FTR] Track process duration + test stats in run-end","number":238397,"url":"https://github.com/elastic/kibana/pull/238397","mergeCommit":{"message":"[FTR] Track process duration + test stats in run-end (#238397)\n\nCurrently we only measure the root suite duration, which does not\ninclude the time to start Elasticsearch, Kibana (which are started\nbefore Mocha runs) and the docker containers (which are in the\n`beforeTests` lifecycle).\n\nWith this change, we start tracking A) total process duration which will\ncapture these phases, B) test stats, so we can see the distribution of\ntest counts across configs and the relation between test counts and\nprocess/test run duration","sha":"086c2900f274de0239dccb82595b93a883fa946b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/238397","number":238397,"mergeCommit":{"message":"[FTR] Track process duration + test stats in run-end (#238397)\n\nCurrently we only measure the root suite duration, which does not\ninclude the time to start Elasticsearch, Kibana (which are started\nbefore Mocha runs) and the docker containers (which are in the\n`beforeTests` lifecycle).\n\nWith this change, we start tracking A) total process duration which will\ncapture these phases, B) test stats, so we can see the distribution of\ntest counts across configs and the relation between test counts and\nprocess/test run duration","sha":"086c2900f274de0239dccb82595b93a883fa946b"}}]}] BACKPORT--> Co-authored-by: Dario Gieselaar <dario.gieselaar@elastic.co>
kibanamachine
added a commit
that referenced
this pull request
Oct 14, 2025
…238924) # Backport This will backport the following commits from `main` to `9.2`: - [[FTR] Track process duration + test stats in run-end (#238397)](#238397) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dario Gieselaar","email":"dario.gieselaar@elastic.co"},"sourceCommit":{"committedDate":"2025-10-14T14:36:17Z","message":"[FTR] Track process duration + test stats in run-end (#238397)\n\nCurrently we only measure the root suite duration, which does not\ninclude the time to start Elasticsearch, Kibana (which are started\nbefore Mocha runs) and the docker containers (which are in the\n`beforeTests` lifecycle).\n\nWith this change, we start tracking A) total process duration which will\ncapture these phases, B) test stats, so we can see the distribution of\ntest counts across configs and the relation between test counts and\nprocess/test run duration","sha":"086c2900f274de0239dccb82595b93a883fa946b","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.3.0"],"title":"[FTR] Track process duration + test stats in run-end","number":238397,"url":"https://github.com/elastic/kibana/pull/238397","mergeCommit":{"message":"[FTR] Track process duration + test stats in run-end (#238397)\n\nCurrently we only measure the root suite duration, which does not\ninclude the time to start Elasticsearch, Kibana (which are started\nbefore Mocha runs) and the docker containers (which are in the\n`beforeTests` lifecycle).\n\nWith this change, we start tracking A) total process duration which will\ncapture these phases, B) test stats, so we can see the distribution of\ntest counts across configs and the relation between test counts and\nprocess/test run duration","sha":"086c2900f274de0239dccb82595b93a883fa946b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/238397","number":238397,"mergeCommit":{"message":"[FTR] Track process duration + test stats in run-end (#238397)\n\nCurrently we only measure the root suite duration, which does not\ninclude the time to start Elasticsearch, Kibana (which are started\nbefore Mocha runs) and the docker containers (which are in the\n`beforeTests` lifecycle).\n\nWith this change, we start tracking A) total process duration which will\ncapture these phases, B) test stats, so we can see the distribution of\ntest counts across configs and the relation between test counts and\nprocess/test run duration","sha":"086c2900f274de0239dccb82595b93a883fa946b"}}]}] BACKPORT--> Co-authored-by: Dario Gieselaar <dario.gieselaar@elastic.co>
ersin-erdal
pushed a commit
to ersin-erdal/kibana
that referenced
this pull request
Oct 15, 2025
Currently we only measure the root suite duration, which does not include the time to start Elasticsearch, Kibana (which are started before Mocha runs) and the docker containers (which are in the `beforeTests` lifecycle). With this change, we start tracking A) total process duration which will capture these phases, B) test stats, so we can see the distribution of test counts across configs and the relation between test counts and process/test run duration
mgadewoll
pushed a commit
to tkajtoch/kibana
that referenced
this pull request
Oct 17, 2025
Currently we only measure the root suite duration, which does not include the time to start Elasticsearch, Kibana (which are started before Mocha runs) and the docker containers (which are in the `beforeTests` lifecycle). With this change, we start tracking A) total process duration which will capture these phases, B) test stats, so we can see the distribution of test counts across configs and the relation between test counts and process/test run duration
rylnd
pushed a commit
to rylnd/kibana
that referenced
this pull request
Oct 17, 2025
Currently we only measure the root suite duration, which does not include the time to start Elasticsearch, Kibana (which are started before Mocha runs) and the docker containers (which are in the `beforeTests` lifecycle). With this change, we start tracking A) total process duration which will capture these phases, B) test stats, so we can see the distribution of test counts across configs and the relation between test counts and process/test run duration
nickpeihl
pushed a commit
to nickpeihl/kibana
that referenced
this pull request
Oct 23, 2025
Currently we only measure the root suite duration, which does not include the time to start Elasticsearch, Kibana (which are started before Mocha runs) and the docker containers (which are in the `beforeTests` lifecycle). With this change, we start tracking A) total process duration which will capture these phases, B) test stats, so we can see the distribution of test counts across configs and the relation between test counts and process/test run duration
NicholasPeretti
pushed a commit
to NicholasPeretti/kibana
that referenced
this pull request
Oct 27, 2025
Currently we only measure the root suite duration, which does not include the time to start Elasticsearch, Kibana (which are started before Mocha runs) and the docker containers (which are in the `beforeTests` lifecycle). With this change, we start tracking A) total process duration which will capture these phases, B) test stats, so we can see the distribution of test counts across configs and the relation between test counts and process/test run duration
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently we only measure the root suite duration, which does not include the time to start Elasticsearch, Kibana (which are started before Mocha runs) and the docker containers (which are in the
beforeTestslifecycle).With this change, we start tracking A) total process duration which will capture these phases, B) test stats, so we can see the distribution of test counts across configs and the relation between test counts and process/test run duration