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
[mu bug] 1.12.0 test failures #2631
Comments
Yes, we test locally and in CI (Ubuntu & MacOS): I suspect the |
The exact commands used to set up the environment and run the build and test can be found in the full build log I included in the first post, more specifically: Build comamnd: https://gist.github.com/manphiz/76fe2b46cc685736fc9ce7bbefee3593#file-maildir-utils_1-12-0-1_amd64-2024-02-25t00-51-07z-build-L1399 |
Hmm, I don't have the required setup, nor the time to set it up right now, let alone tracking down the specific problem. |
Turns out that to correctly handle all the unicode we do need a more full fledged locales environment. After fixing the dependencies in the Debian build control, the Test log regarding the failed tests:
Full build log: https://gist.github.com/manphiz/cb253a234cd1fadfc2c03d7aa74ed8a1#file-maildir-utils_1-12-0-1_amd64-build-L3001 EDIT: more specifically, the generated library can be found at EDIT 2: sent #2635 which I've tested to fix this issue. PTAL. |
I've pushed a small change a few days ago which may help to double-check some locale things. Anyhow, this is working now? Can we close this ticket? |
#2635 should fix this. Any concerns before merging that? |
Describe the bug
3 out of 46 tests fail when building in Debian's chroot environment (sbuild). Though the failures are deterministic, I suspect that this may be due to that the build environment produces different output compared with the Developers. It would be good if the tests are made more robust so that they won't be affected by environment differences.
Full build log: https://gist.github.com/manphiz/76fe2b46cc685736fc9ce7bbefee3593
Environment
Current Debian sid/unstable
Checklist
master
(otherwise, please upgrade).Running 1.12.0
The text was updated successfully, but these errors were encountered: