New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check if ports are occupied before start sqlness test #1602
Comments
I'm a little confused about
it that means Sqlness will spawn subprocess? Which file can give me a first look at the problem?
|
Sry,i don't see it has been assigned😭 |
Never mind. We got a ton of the good first issues waiting for you 🤪 |
@Gump9 Are you still interested in this issue? Feel free to take it. |
Yes,can I have a try?tks alot |
and i still want to know more details about this issue i mentioned above |
Yes, sqlness runner will start greptimedb (metasrv/frontend/datanode) to test. You can check it out here greptimedb/tests/runner/src/env.rs Line 124 in fcff66e
|
@waynexia thx a lot😄 |
@waynexia Hi!should i just panic like the code below?because i found "Sqlness only check if the port is up after spawn at present." do something like this: if !util::check_port(check_ip_addr.parse().unwrap(), Duration::from_secs(10)).await {
Env::stop_server(&mut process);
panic!("{subcommand} doesn't up in 10 seconds, quit.")
} or,should i choose another port and try to up a process again? |
|
thx! |
What problem does the new feature solve?
Sqlness uses the common port (e.g.
4000
) to start server. It's common that the port is occupied by other process like another greptimedb process. In this case the test result will become weird because it's actually testing something elseWhat does the feature do?
Check those ports before spawn subprocess. Sqlness only check if the port is up after spawn at present.
Implementation challenges
No response
The text was updated successfully, but these errors were encountered: