Skip to content

IGNITE-29146 Generate JSON files for IDTO - #13730

Open
chesnokoff wants to merge 9 commits into
apache:masterfrom
chesnokoff:ignite-29146
Open

chesnokoff wants to merge 9 commits into
apache:masterfrom
chesnokoff:ignite-29146

Conversation

@chesnokoff

Copy link
Copy Markdown
Contributor

Thank you for submitting the pull request to the Apache Ignite.

In order to streamline the review of the contribution
we ask you to ensure the following steps have been taken:

The Contribution Checklist

  • There is a single JIRA ticket related to the pull request.
  • The web-link to the pull request is attached to the JIRA ticket.
  • The JIRA ticket has the Patch Available state.
  • The pull request body describes changes that have been made.
    The description explains WHAT and WHY was made instead of HOW.
  • The pull request title is treated as the final commit message.
    The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
  • A reviewer has been mentioned through the JIRA comments
    (see the Maintainers list)
  • The pull request has been checked by the Teamcity Bot and
    the green visa attached to the JIRA ticket (see tab PR Check at TC.Bot - Instance 1 or TC.Bot - Instance 2)

Notes

If you need any help, please email dev@ignite.apache.org or ask any advice on https://the-asf.slack.com #ignite channel.

@ignite-pr-checker

ignite-pr-checker commented Oct 22, 2026 •

Copy link
Copy Markdown

Ignite PR Checker verdict · RunAll build 9432303 · tested aef0030 · 149 suites ran, 0 reused

✅ No blockers — nothing in this run looks caused by this PR. 24 failing tests are not blamed on this PR.

What each label means and what to do: verdict glossary.

Posted by ci2 user chesnokoff from the checker's page.

🔁 Superseded by the newer RunAll 9435822 — its verdict is on the checker's page.

@ignite-pr-checker

Copy link
Copy Markdown

Ignite PR Checker verdict · RunAll build 9435822 · tested cbfc0ee · 149 suites ran, 0 reused

⚠️ This run doesn't cover the PR fully:

  • 44 suites ran fewer tests than the same suites on master

Everything below is what it did manage to say.

🔍 44 suites ran fewer tests than on master (tests that never ran can't fail):

  • Cache (Failover) 1: ran 26 of master's 36 tests (−28%)
  • Examples: ran 84 of master's 114 tests (−26%)
  • Cache (Deadlock Detection): ran 33 of master's 44 tests (−25%)
  • JTA: ran 34 of master's 45 tests (−24%)
  • Cache 20: ran 215 of master's 276 tests (−22%)
  • Security: ran 238 of master's 300 tests (−21%)
  • Cache 10: ran 345 of master's 437 tests (−21%)
  • Cache (Failover) 4: ran 38 of master's 48 tests (−21%)
  • Cache (Failover) 5: ran 67 of master's 85 tests (−21%)
  • Compute (Affinity Run): ran 23 of master's 29 tests (−21%)
  • SPI (URI Deploy): ran 55 of master's 69 tests (−20%)
  • Cache (Expiry Policy): ran 136 of master's 171 tests (−20%)
  • Cache 16: ran 319 of master's 395 tests (−19%)
  • Cache 21: ran 209 of master's 258 tests (−19%)
  • Basic 3: ran 165 of master's 202 tests (−18%)
  • Cache 14: ran 193 of master's 233 tests (−17%)
  • NUMA Allocator: ran 17 of master's 20 tests (−15%)
  • Cache 11: ran 162 of master's 191 tests (−15%)
  • Activate / Deactivate Cluster: ran 227 of master's 266 tests (−15%)
  • Cache 2: ran 424 of master's 499 tests (−15%)
  • PDS (Indexing): ran 206 of master's 242 tests (−15%)
  • Cache 7: ran 147 of master's 171 tests (−14%)
  • PDS 10: ran 216 of master's 251 tests (−14%)
  • Disk Page Compressions 8: ran 216 of master's 251 tests (−14%)
  • Cache 18: ran 152 of master's 176 tests (−14%)
  • Cache 3: ran 519 of master's 606 tests (−14%)
  • Cache 6: ran 170 of master's 197 tests (−14%)
  • Data Structures: ran 349 of master's 406 tests (−14%)
  • Queries (Config Variations): ran 288 of master's 336 tests (−14%)
  • Cache 9: ran 79 of master's 91 tests (−13%)
  • PDS 8: ran 249 of master's 285 tests (−13%)
  • SPI (Discovery) 2: ran 296 of master's 340 tests (−13%)
  • Dev Utils: ran 29 of master's 33 tests (−12%)
  • Calcite SQL 2: ran 1242 of master's 1406 tests (−12%)
  • PDS (Indexing) 2: ran 200 of master's 227 tests (−12%)
  • Cache (Tx Recovery): ran 93 of master's 106 tests (−12%)
  • PDS 4: ran 213 of master's 239 tests (−11%)
  • Service Grid: ran 401 of master's 451 tests (−11%)
  • Thin Client: Java: ran 443 of master's 495 tests (−11%)
  • Basic 4: ran 710 of master's 796 tests (−11%)
  • SPI (Discovery): ran 281 of master's 317 tests (−11%)
  • Web Sessions: ran 54 of master's 60 tests (−10%)
  • Queries 3: ran 1499 of master's 1671 tests (−10%)
  • Disk Page Compressions 6: ran 117 of master's 130 tests (−10%)

🔎 No blockers found — but the run above can't prove the PR is clean. 32 failing tests are not blamed on this PR. Re-run after you handle what is listed above.

What each label means and what to do: verdict glossary.

Posted by ci2 user chesnokoff from the checker's page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants