Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CAMEL-21438: disable unreliable tests on multiple platforms #16234

Merged
merged 1 commit into from
Nov 12, 2024
Merged

CAMEL-21438: disable unreliable tests on multiple platforms #16234

merged 1 commit into from
Nov 12, 2024
+35 −6

Conversation

orpiske
Copy link
Contributor

@orpiske orpiske commented Nov 12, 2024

No description provided.

@github-actions GitHub Actions
Copy link
Contributor

🌟 Thank you for your contribution to the Apache Camel project! 🌟

🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

  • First-time contributors require MANUAL approval for the GitHub Actions to run

  • You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot.

  • You can label PRs using build-all, build-dependents, skip-tests and test-dependents to fine-tune the checks executed by this PR.

  • Build and test logs are available in the Summary page. Only Apache Camel committers have access to the summary.

  • ⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

@orpiske orpiske changed the title CAMEL-21438: disable unreliable tests on s390x CAMEL-21438: disable unreliable tests on multiple platforms Nov 12, 2024
@orpiske orpiske merged commit 1cc771f into apache:main Nov 12, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@oscerd oscerd oscerd approved these changes

Assignees
No one assigned
Labels
camel-4 components core
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@orpiske @oscerd