[test] Unstable test after DefaultAuthorizerTest
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 625
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 97
Description
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.
### Fluss version
0.9.0 (latest release)
### Please describe the bug 🐞
Unstable test in DefaultAuthorizerTest.
```
Error: pure virtual method called
Error: terminate called without an active exception
```
https://github.com/apache/fluss/actions/runs/26512378596/job/78079836867?pr=3391
### Solution
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by running DefaultAuthorizerTest repeatedly and compare its behavior with the linked GitHub Actions run. Trace the test and its setup around the reported “pure virtual method called” failure; done means the test completes reliably without the termination error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authorization, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100