-
Notifications
You must be signed in to change notification settings - Fork 182
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
Test failings because test.yml strings present in file are not found. #2118
Comments
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc6 in position 764: invalid continuation byte Seems to me like this may actually be an issue where it fails to decode the file but the eventual "failure" is just reported as the value not being present? |
I'm not sure what I can do about those funky characters. What's the protocol here then? |
Probably the only actual solution is to open an issue with They could maybe just use |
The problem is that some file is apparently written with utf-16 and then read as utf-8. I think it would make sense to try and define the encoding upon file creation. |
Not sure how to change that then. The
I even ran a |
I would assume it's down to the So personally I still think getting the testing framework to allow multiple encodings is better than trying to persuade each individual tool maintainer to output only in |
I think you're right there. I'm not sure though it's something I can chase up though particularly as I'm technically on leave now. I think though, from the perspective here, that this is something that can't be solved. Checking for file existence is OK for the moment. Perhaps if/when nf-test is rolled out across modules, it'll be possible there. Thanks for investigating though. |
I just tried running the test on my machine - and they all pass. What profile did you use for the tests? Here's my locale - maybe it can help you:
|
Including with the contains that was removed? |
That's what I did:
I think I know what you mean now - the failing tests are not in the module? |
Exactly. The part that fails is not included in the module. It's only described above |
OK, this log is malformed. This should probably be reported to the purgedups devs. The generated file is a malformed UTF-8 file. See attachment. |
LUMC/pytest-workflow#161 (comment) pytest-workflow now implements an encoding specifier. In this case I believe it to be "latin-1". |
Description of the bug
https://github.com/nf-core/modules/actions/runs/3657880825/jobs/6181972088
The test workflow fails to find the strings in a file even though the output is there:
but the log file looks like:
Command used and terminal output
System information
Nextflow version: version 22.10.1
Hardware: Cloud (Gitpod)
Executor: local
OS: Unix (Gitpod)
nf-core/tools: 2.7.1
python: 3.9.15
The text was updated successfully, but these errors were encountered: