Track issue for expression test cases generated by LLM
- Dominant language
- Go
- Stars
- 40.5k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
I'm trying to generate test cases for expression through LLM. In this issue, I'll track all issues and error cases found by this method. The description will included all sub-issues, and the failed test cases will be added to the comment.
Some of them may be duplicated, I didn't search the github before creating the issue (sorry). Feel free to close them if you find it's duplicated.
- [ ] https://github.com/pingcap/tidb/issues/59411
- [ ] https://github.com/pingcap/tidb/issues/59412
- [ ] https://github.com/pingcap/tidb/issues/59413
- [ ] https://github.com/pingcap/tidb/issues/59414
- [ ] https://github.com/pingcap/tidb/issues/59415
- [ ] https://github.com/pingcap/tidb/issues/59416
- [x] https://github.com/pingcap/tidb/issues/59417
- [ ] https://github.com/pingcap/tidb/issues/59418
- [ ] https://github.com/pingcap/tidb/issues/59419
- [x] https://github.com/pingcap/tidb/issues/59420
- [ ] https://github.com/pingcap/tidb/issues/59421
- [ ] https://github.com/pingcap/tidb/issues/59423
- [ ] https://github.com/pingcap/tidb/issues/59424
- [ ] https://github.com/pingcap/tidb/issues/59425
- [ ] https://github.com/pingcap/tidb/issues/59426
- [x] https://github.com/pingcap/tidb/issues/59428
- [ ] https://github.com/pingcap/tidb/issues/59429
- [ ] https://github.com/pingcap/tidb/issues/59430
- [ ] https://github.com/pingcap/tidb/issues/59431
- [ ] https://github.com/pingcap/tidb/issues/59432
- [ ] https://github.com/pingcap/tidb/issues/59433
- [ ] https://github.com/pingcap/tidb/issues/59434
- [ ] https://github.com/pingcap/tidb/issues/59435
- [ ] https://github.com/pingcap/tidb/issues/59436
- [ ] https://github.com/pingcap/tidb/issues/59437
- [ ] https://github.com/pingcap/tidb/issues/59438
- [ ] https://github.com/pingcap/tidb/issues/59439
- [ ] https://github.com/pingcap/tidb/issues/59440
- [ ] https://github.com/pingcap/tidb/issues/59441
- [ ] https://github.com/pingcap/tidb/issues/59442
- [ ] https://github.com/pingcap/tidb/issues/59443
- [x] https://github.com/pingcap/tidb/issues/59444
- [x] https://github.com/pingcap/tidb/issues/59445
- [x] https://github.com/pingcap/tidb/issues/59446
- [x] https://github.com/pingcap/tidb/issues/59447
- [ ] https://github.com/pingcap/tidb/issues/59448
- [ ] https://github.com/pingcap/tidb/issues/59449
- [ ] https://github.com/pingcap/tidb/issues/59450
- [ ] https://github.com/pingcap/tidb/issues/59451
- [ ] https://github.com/pingcap/tidb/issues/59452
- [x] https://github.com/pingcap/tidb/issues/59453
- [ ] https://github.com/pingcap/tidb/issues/59454
- [ ] https://github.com/pingcap/tidb/issues/59455
- [x] https://github.com/pingcap/tidb/issues/59456
- [x] https://github.com/pingcap/tidb/issues/59457
- [ ] https://github.com/pingcap/tidb/issues/59458
- [ ] https://github.com/pingcap/tidb/issues/59459
- [ ] https://github.com/pingcap/tidb/issues/59460
- [ ] https://github.com/pingcap/tidb/issues/59461
- [ ] https://github.com/pingcap/tidb/issues/59462
- [x] https://github.com/pingcap/tidb/issues/59463
- [ ] https://github.com/pingcap/tidb/issues/59464
- [x] https://github.com/pingcap/tidb/issues/59465
- [x] https://github.com/pingcap/tidb/issues/59617
- [ ] https://github.com/pingcap/tidb/issues/59618
- [x] https://github.com/pingcap/tidb/issues/59619
- [ ] https://github.com/pingcap/tidb/issues/59620
- [ ] https://github.com/pingcap/tidb/issues/59621
- [ ] https://github.com/pingcap/tidb/issues/59622
- [x] https://github.com/pingcap/tidb/issues/59623
- [ ] https://github.com/pingcap/tidb/issues/59624
- [ ] https://github.com/pingcap/tidb/issues/59785
- [ ] https://github.com/pingcap/tidb/issues/59786
- [ ] https://github.com/pingcap/tidb/issues/59787
- [x] https://github.com/pingcap/tidb/issues/59788
- [ ] https://github.com/pingcap/tidb/issues/59789
- [ ] https://github.com/pingcap/tidb/issues/59790
Contributor guide
Research direction
Start by reviewing the linked sub-issues and the failed test cases recorded in this issue's comments. The scope is a broad tracker rather than a single code change; completion would require resolving or closing the remaining sub-issues and updating the checklist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- databases, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100