Skip to content
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

[Merged by Bors] - Try possible fix for flaky TestAdminEvents on Windows #5165

Closed
wants to merge 1 commit into from

Conversation

fasmat
Copy link
Member

@fasmat fasmat commented Oct 17, 2023

Motivation

Instead of trying to access the local PoET via 0.0.0.0:10010 access it via 127.0.0.1:10010. The first address seems to cause problems on some Windows systems

Changes

Updated standalone config to use 127.0.0.1 for local addresses instead of 0.0.0.0

Test Plan

n/a

TODO

  • Explain motivation or link existing issue(s)
  • Test changes and document test plan
  • Update documentation as needed
  • Update changelog as needed

@codecov
Copy link

codecov bot commented Oct 17, 2023

Codecov Report

Merging #5165 (dc07a45) into develop (156d084) will increase coverage by 0.1%.
Report is 2 commits behind head on develop.
The diff coverage is 100.0%.

@@            Coverage Diff            @@
##           develop   #5165     +/-   ##
=========================================
+ Coverage     77.6%   77.7%   +0.1%     
=========================================
  Files          259     259             
  Lines        30457   30750    +293     
=========================================
+ Hits         23644   23909    +265     
- Misses        5322    5350     +28     
  Partials      1491    1491             
Files Coverage Δ
config/presets/standalone.go 100.0% <100.0%> (ø)

... and 6 files with indirect coverage changes

@fasmat
Copy link
Member Author

fasmat commented Oct 17, 2023

bors merge

bors bot pushed a commit that referenced this pull request Oct 17, 2023
## Motivation
Instead of trying to access the local PoET via `0.0.0.0:10010` access it via `127.0.0.1:10010`. The first address seems to cause problems on some Windows systems

## Changes
Updated standalone config to use 127.0.0.1 for local addresses instead of 0.0.0.0

## Test Plan
n/a

## TODO
<!-- This section should be removed when all items are complete -->
- [x] Explain motivation or link existing issue(s)
- [x] Test changes and document test plan
- [x] Update documentation as needed
- [x] Update [changelog](../CHANGELOG.md) as needed
@bors
Copy link

bors bot commented Oct 17, 2023

Pull request successfully merged into develop.

Build succeeded!

The publicly hosted instance of bors-ng is deprecated and will go away soon.

If you want to self-host your own instance, instructions are here.
For more help, visit the forum.

If you want to switch to GitHub's built-in merge queue, visit their help page.

@bors bors bot changed the title Try possible fix for flaky TestAdminEvents on Windows [Merged by Bors] - Try possible fix for flaky TestAdminEvents on Windows Oct 17, 2023
@bors bors bot closed this Oct 17, 2023
@bors bors bot deleted the fix-flaky-TestAdminEvents branch October 17, 2023 09:16
poszu pushed a commit that referenced this pull request Oct 17, 2023
## Motivation
Instead of trying to access the local PoET via `0.0.0.0:10010` access it via `127.0.0.1:10010`. The first address seems to cause problems on some Windows systems

## Changes
Updated standalone config to use 127.0.0.1 for local addresses instead of 0.0.0.0

## Test Plan
n/a

## TODO
<!-- This section should be removed when all items are complete -->
- [x] Explain motivation or link existing issue(s)
- [x] Test changes and document test plan
- [x] Update documentation as needed
- [x] Update [changelog](../CHANGELOG.md) as needed
bors bot pushed a commit that referenced this pull request Oct 19, 2023
…5172)

## Motivation
Follow up to #5165

Additionally to Windows not liking `0.0.0.0` as connection address, the Windows GH runners sometimes disallow to listen on port 50002 (default for PoET gRPC). It seems to be an issue with some of the windows runners, since no other test uses a standalone PoET (so nothing should be listening there already) and it only appears to happen on Windows. Assigning a random (free) port as listen address seems generally a good idea (for parallelisation, less likely to fail, etc.)

## Changes
- changed `RawRPCListener` to use a random port instead of the default one if node is launched in standalone mode

## Test Plan
n/a

## TODO
<!-- This section should be removed when all items are complete -->
- [x] Explain motivation or link existing issue(s)
- [x] Test changes and document test plan
- [x] Update documentation as needed
- [x] Update [changelog](../CHANGELOG.md) as needed
bors bot pushed a commit that referenced this pull request Oct 19, 2023
…5172)

## Motivation
Follow up to #5165

Additionally to Windows not liking `0.0.0.0` as connection address, the Windows GH runners sometimes disallow to listen on port 50002 (default for PoET gRPC). It seems to be an issue with some of the windows runners, since no other test uses a standalone PoET (so nothing should be listening there already) and it only appears to happen on Windows. Assigning a random (free) port as listen address seems generally a good idea (for parallelisation, less likely to fail, etc.)

## Changes
- changed `RawRPCListener` to use a random port instead of the default one if node is launched in standalone mode

## Test Plan
n/a

## TODO
<!-- This section should be removed when all items are complete -->
- [x] Explain motivation or link existing issue(s)
- [x] Test changes and document test plan
- [x] Update documentation as needed
- [x] Update [changelog](../CHANGELOG.md) as needed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants