pingcap / pingcap/tiflash

fullstack-test2/diagnostics/check_diagnostics.test unstable

Open
#8,416 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

affects-8.1 affects-8.5 component/compute may-affects-5.4 may-affects-6.1 may-affects-6.5 may-affects-7.1 may-affects-7.5 severity/major type/bug
Dominant language
C++
Stars
1k
Forks
423
Avg merge
1d 15h
Merged PRs (30d)
24

Description

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

https://ci.pingcap.net/blue/organizations/jenkins/tiflash-ghpr-integration-tests/detail/tiflash-ghpr-integration-tests/15186/pipeline/128

[2023-11-23T09:09:50.447Z] fullstack-test2/diagnostics/check_diagnostics.test: Running

[2023-11-23T09:10:08.503Z]   File: fullstack-test2/diagnostics/check_diagnostics.test

[2023-11-23T09:10:08.503Z]   Error line: 15

[2023-11-23T09:10:08.503Z]   Error: select distinct(NAME) from INFORMATION_SCHEMA.CLUSTER_HARDWARE where TYPE='tiflash' order by NAME;

[2023-11-23T09:10:08.503Z]   Result:

[2023-11-23T09:10:08.503Z]     <nothing>

[2023-11-23T09:10:08.503Z]   Expected:

[2023-11-23T09:10:08.503Z]     +--------------------+

[2023-11-23T09:10:08.503Z]     | NAME               |

[2023-11-23T09:10:08.503Z]     +--------------------+

[2023-11-23T09:10:08.503Z]     | capacity           |

[2023-11-23T09:10:08.503Z]     | cpu-arch           |

[2023-11-23T09:10:08.503Z]     | cpu-frequency      |

[2023-11-23T09:10:08.503Z]     | cpu-logical-cores  |

[2023-11-23T09:10:08.503Z]     | cpu-physical-cores |

[2023-11-23T09:10:08.503Z]     | cpu-vendor-id      |

[2023-11-23T09:10:08.503Z]     | flag               |

[2023-11-23T09:10:08.503Z]     | free               |

[2023-11-23T09:10:08.503Z]     | free-percent       |

[2023-11-23T09:10:08.503Z]     | fstype             |

[2023-11-23T09:10:08.503Z]     | index              |

[2023-11-23T09:10:08.503Z]     | ip                 |

[2023-11-23T09:10:08.503Z]     | is-broadcast       |

[2023-11-23T09:10:08.503Z]     | is-loopback        |

[2023-11-23T09:10:08.503Z]     | is-multicast       |

[2023-11-23T09:10:08.503Z]     | is-point-to-point  |

[2023-11-23T09:10:08.503Z]     | is-up              |

[2023-11-23T09:10:08.503Z]     | l1-cache-line-size |

[2023-11-23T09:10:08.503Z]     | l1-cache-size      |

[2023-11-23T09:10:08.503Z]     | l2-cache-line-size |

[2023-11-23T09:10:08.503Z]     | l2-cache-size      |

[2023-11-23T09:10:08.503Z]     | l3-cache-line-size |

[2023-11-23T09:10:08.503Z]     | l3-cache-size      |

[2023-11-23T09:10:08.503Z]     | mac                |

[2023-11-23T09:10:08.503Z]     | path               |

[2023-11-23T09:10:08.503Z]     | total              |

[2023-11-23T09:10:08.503Z]     | type               |

[2023-11-23T09:10:08.503Z]     | used               |

[2023-11-23T09:10:08.503Z]     | used-percent       |

[2023-11-23T09:10:08.503Z]     +--------------------+
2. What did you expect to see? (Required)
3. What did you see instead (Required)
4. What is your TiFlash version? (Required)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with fullstack-test2/diagnostics/check_diagnostics.test and the linked CI pipeline, focusing on the query at error line 15 against INFORMATION_SCHEMA.CLUSTER_HARDWARE. Reproduce the failure and compare the empty result with the listed expected names; done means the unstable test has a reliable, justified result.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql
Domain
databases, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.