Skip to content

Conversation

badochov
Copy link
Contributor

JIRA: RTOS-1002

Description

Motivation and Context

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (refactoring, style fixes, git/CI config, submodule management, no code logic changes)

How Has This Been Tested?

  • Already covered by automatic testing.
  • New test added: (add PR link here).
  • Tested by hand on: ia32

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing linter checks and tests passed.
  • My changes generate no new compilation warnings for any of the targets.

Special treatment

  • This PR needs additional PRs to work (list the PRs, preferably in merge-order).
  • I will merge this PR by myself when appropriate.

JIRA: RTOS-1002
@badochov badochov requested a review from Darchiv January 29, 2025 16:30
Copy link

Unit Test Results

7 958 tests  +948   7 416 ✅ +881   40m 5s ⏱️ + 5m 37s
  470 suites + 58     542 💤 + 67 
    1 files   ±  0       0 ❌ ±  0 

Results for commit 340607e. ± Comparison against base commit efb2406.

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.

1 participant