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

fix: unit test scanner_scan_proc utf-16 encoding #30

Merged
merged 1 commit into from May 28, 2021

Conversation

Orycterope
Copy link
Contributor

An attempt to fix #25 by extending the timeout. Let's see if it works.

@Orycterope
Copy link
Contributor Author

Aaaand the test still fails, so seems it's not a timeout problem ...

I really don't get it, and I can't manage to reproduce it on my windows VM. Do you encounter it on any of your machines ?

@Hugal31
Copy link
Owner

Hugal31 commented May 26, 2021

I don't usually code on Windows, so I've never tried to reproduced it.

@Orycterope
Copy link
Contributor Author

Maybe this is an encoding problem with the needle string ? (Yes I'm desperate at this point)

@Orycterope Orycterope changed the title fix: unit test scanner_scan_proc longer timeout fix: unit test scanner_scan_proc utf-16 encoding May 28, 2021
@Orycterope
Copy link
Contributor Author

Orycterope commented May 28, 2021

So this was an encoding problem ! On windows, the string is present in cmd's memory, but only in utf-16 format. I've updated the test case to look only for wide strings on windows.

The test worked in my windows VM because somehow the string must have been also present in utf-8 form.

I've kept the longer timeout, cause we never know

@Hugal31
Copy link
Owner

Hugal31 commented May 28, 2021

Good catch! Thank you very much!

@Hugal31 Hugal31 merged commit f8b4e53 into Hugal31:master May 28, 2021
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.

scanner::test::scanner_scan_proc fails randomly on Windows
2 participants