apache / apache/incubator-seata

RedisDistributedLockerTest.test_acquireScheduledLock_success UT failed.

Open
#5,949 1 comment 0 reactions 0 assignees View on GitHub
task: help-wanted
Dominant language
Java
Stars
26k
Forks
8.8k
Avg merge
1d 8h
Merged PRs (30d)
4

Description

- [ ] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate.

### Ⅰ. Issue Description
![image](https://github.com/seata/seata/assets/8758457/a86b782d-4585-4329-a00c-48168a2e1692)
https://github.com/seata/seata/actions/runs/6604746563/job/17939197694

### Ⅱ. Describe what happened

If there is an exception, please attach the exception trace:

```
Just paste your stack trace here!
```

### Ⅲ. Describe what you expected to happen

### Ⅳ. How to reproduce it (as minimally and precisely as possible)

1. xxx
2. xxx
3. xxx

Minimal yet complete reproducer code (or URL to code):

### Ⅴ. Anything else we need to know?

### Ⅵ. Environment:

- JDK version(e.g. `java -version`):
- Seata client/server version:
- Database version:
- OS(e.g. `uname -a`):
- Others:

Contributor guide

Open the contributing guide

Research direction

Start with the linked GitHub Actions run and the RedisDistributedLockerTest.test_acquireScheduledLock_success failure. Reproduce the test in the repository's Java test environment and inspect the available failure details. Done means the test passes reliably and the underlying cause of the reported failure is addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, redis
Domain
distributed-systems, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.