Skip to content

Conversation

forsaken628
Copy link
Collaborator

@forsaken628 forsaken628 commented Sep 29, 2025

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

Tests

  • Unit Test
  • Logic Test
  • Benchmark Test
  • No Test - Explain why

Type of change

  • Bug Fix (non-breaking change which fixes an issue)
  • New Feature (non-breaking change which adds functionality)
  • Breaking Change (fix or feature that could cause existing functionality not to work as expected)
  • Documentation Update
  • Refactoring
  • Performance Improvement
  • Other (please describe):

This change is Reviewable

Copy link
Contributor

github-actions bot commented Sep 29, 2025

At least one test kind must be checked in the PR description.
@forsaken628 please update it 🙏.

@github-actions github-actions bot added the pr-feature this PR introduces a new feature to the codebase label Sep 29, 2025
Copy link
Contributor

github-actions bot commented Sep 29, 2025

At least one type of change must be checked in the PR description.
@forsaken628 please update it 🙏.

Copy link
Contributor

github-actions bot commented Oct 9, 2025

🤖 Smart Auto-retry Analysis

Workflow: 18374898785

📊 Summary

  • Total Jobs: 23
  • Failed Jobs: 2
  • Retryable: 0
  • Code Issues: 2

NO RETRY NEEDED

All failures appear to be code/test issues requiring manual fixes.

🔍 Job Details

  • linux / test_unit: Not retryable (Code/Test)
  • linux / check: Not retryable (Code/Test)

🤖 About

Automated analysis using job annotations to distinguish infrastructure issues (auto-retried) from code/test issues (manual fixes needed).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr-feature this PR introduces a new feature to the codebase
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant