Skip to content

Investigate windows failure in rpc_conflict test #3666

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

Closed
oxarbitrage opened this issue Feb 28, 2022 · 4 comments
Closed

Investigate windows failure in rpc_conflict test #3666

oxarbitrage opened this issue Feb 28, 2022 · 4 comments
Labels
C-bug Category: This is a bug

Comments

@oxarbitrage
Copy link
Contributor

oxarbitrage commented Feb 28, 2022

Motivation

In #3641 we added an rpc_conflict test to check an already in use port for the rpc server.

This test is failing on windows: #3641 (comment)

Scheduling

We are disabling the test for windows family but we will want to know what is going on exactly with it and potentially fix and enable the test for this platform.

We only need to schedule this ticket if we decide to support Windows as a primary platform.

@oxarbitrage oxarbitrage added C-bug Category: This is a bug S-needs-triage Status: A bug report needs triage labels Feb 28, 2022
@ftm1000
Copy link

ftm1000 commented Feb 28, 2022

@teor2345
Copy link
Contributor

We only need to schedule this ticket if we decide to support Windows as a primary platform.

(We seemed to only want to promise primary support for Linux last time we talked.)

@gustavovalverde
Copy link
Member

That's correct. And we even have to workaround some issues with Docker and Rust while using Windows rust-lang/docker-rust#30

@teor2345 teor2345 changed the title Investigate windows failure in rpc_conflic test Investigate windows failure in rpc_conflict test Mar 1, 2022
@ftm1000 ftm1000 removed the S-needs-triage Status: A bug report needs triage label Mar 7, 2022
@oxarbitrage
Copy link
Contributor Author

We are not supporting windows anymore by now, we can reopen if we decide to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug
Projects
None yet
Development

No branches or pull requests

4 participants