Skip to content

Disabled MCPIT because of issue #2340 - #1879

Merged
rsvoboda merged 1 commit into
quarkus-qe:mainfrom
rsvoboda:MCPIT.disable
Apr 17, 2026
Merged

rsvoboda merged 1 commit into
quarkus-qe:mainfrom
rsvoboda:MCPIT.disable

Conversation

@rsvoboda

Copy link
Copy Markdown
Member

Summary

Disabled MCPIT because of issue #2340

quarkiverse/quarkus-langchain4j#2340

Please check the relevant options

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Dependency update
  • Refactoring
  • Release (follows conventions described in the RELEASE.md)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • This change requires a documentation update
  • This change requires execution against Kubernetes (use run kubernetes phrase in comment)
  • This change requires execution against OCP (use run tests phrase in comment)

Checklist:

  • Example scenarios has been updated / added
  • Methods and classes used in PR scenarios are meaningful
  • Commits are well encapsulated and follow the best practices

@rsvoboda
rsvoboda requested review from jedla97 and removed request for fedinskiy April 17, 2026 13:09

@jedla97 jedla97 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rsvoboda I see that in today run it was green again. Do we want to disable it?

@rsvoboda

Copy link
Copy Markdown
Member Author

The issue is valid
tbh I don't know how it could pass, probably snapshots collison of the platform

@rsvoboda

Copy link
Copy Markdown
Member Author

CC @fedinskiy about possible collision of the local build vs. sonatype platform snapshot

@rsvoboda
rsvoboda merged commit 4eb5b3b into quarkus-qe:main Apr 17, 2026
5 checks passed
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