Skip to content

Conversation

@tiginamaria
Copy link
Contributor

@tiginamaria tiginamaria commented Dec 4, 2025

Motivation and Context

How Has This Been Tested?

Breaking Changes

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)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

@github-actions
Copy link

github-actions bot commented Dec 4, 2025

TestsPassed ✅Skipped ⚠️FailedTime ⏱
JUnit Test Report3417 ran3328 passed89 skipped4m 12s 994ms
TestResultTime ⏱
No test annotations available

@kpavlov kpavlov force-pushed the tigina/notification-tests-fix branch from 6f35f8f to a5179df Compare December 5, 2025 17:10
@kpavlov
Copy link
Contributor

kpavlov commented Dec 5, 2025

@tiginamaria , let's run lint on ServerResourcesNotificationSubscribeTest.kt

@kpavlov kpavlov added the tests label Dec 5, 2025
@tiginamaria tiginamaria force-pushed the tigina/notification-tests-fix branch from a5179df to 347626c Compare December 8, 2025 11:59
@kpavlov kpavlov marked this pull request as ready for review December 8, 2025 12:09
@kpavlov kpavlov merged commit 274089a into main Dec 8, 2025
5 checks passed
@kpavlov kpavlov deleted the tigina/notification-tests-fix branch December 8, 2025 12:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants