-
Notifications
You must be signed in to change notification settings - Fork 24
test: test unix addrs #60
Conversation
a4cbc81 to
1b2246d
Compare
|
These test are only being run on Linux, they fail on Windows. I'm seeing similar behavior even with same slashed paths, in the 9P branch. Edit: |
* Convert to windows paths when converting from a multiaddr to a net.Addr * Convert from windows paths when converting from a net.Addr to a multiaddr Also, don't "clean". `filepath.Clean` is _usually_ correct but not _technically_ correct in all cases. We should leave cleaning to the application.
|
Hm. We really need to get windows tests working. Could you test it now? |
|
Better, but not best. The string seems to be converted correctly, but we still need to see where/why this is failing with a seemingly correct argument. Edit: The other test is upset with the slash differences now though. |
|
I'm wondering if the leading slash is being passed to something, or if that's just the target component of the multiaddr being returned in an error. We can either add Windows specific logic to detect and strip this leading slash, or potentially convert to UNC path syntax |
The leading slash is coming from the multiaddr. We start with |
|
Attempting to upgrade the addr string to a UNC path did not seem to resolve this. |
|
@Stebalien I don't have push permissions for this brach Regardless of the source argument, we were passing With that applied, the string tests are still unhappy Reverting d66032c Additonal context: |
|
@djdv I think I've fixed the tests. I've also added you to the org. |
|
The compare string was being escaped, I used a backtick to preserve the literal |
djdv
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests are passing in CI and on Windows
|
Thanks! |
1 similar comment
|
Thanks! |
No description provided.