Starting with vim version 9.1.2103, a lot of tests are failing on 32-bit big-endian targets such as PowerPC:
Version 9.1.1882 still passed all the tests on the same platform:
CC @thesamesam
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Well, 9.1.2103 simply changed how some newly opened buffers are closed. I don't think that this patch actually causes the failures. Can you bisect the offending patch?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
OK, I will give the bisect a try.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Is this the same as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091729 ? In any case, I see @jamessan has successfully uploaded v9.2.0315 to sid, so I assume we can close this issue here.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Is this the same as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091729 ?
No, that's a separate package that fails its tests with newer Vim versions. I think that's related to #16247, which I don't believe has been resolved. I had reverted 9.1.0949 for a while in Debian's package to avoid breaking YCM, but that recently started breaking Vim's test suite, so the latest upload stopped reverting the patch.
The issues @glaubitz are referring to are in Vim's own test suite. These are failing on Debian's unofficial ports, so they've been lower on my priority list to look into.
Looking at the full build log, I hadn't realized just how broad the test failures were.
Executed: 7691 Tests
Skipped: 115 Tests
FAILED: 878 Tests
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Yeah, I was surprised by the amount of failing tests. That must be something fundamentally broken.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Yeah, I was surprised by the amount of failing tests. That must be something fundamentally broken.
Well, it worked with 9.1.1882, so I don't think it's fundamentally broken. I can verify whether that version still builds fine.
image.png (view on web)—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
well 10% failing tests is worrying, especially since we do not see this here in our CI. So that's why it would be important to find which commit broke powerpc setup.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()