-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
feat(core): ldml marker normalization 🙀 #9761
feat(core): ldml marker normalization 🙀 #9761
Conversation
User Test ResultsTest specification and instructions User tests are not required Test Artifacts
|
247ce11
to
8796b50
Compare
moved the failing bengali test case here for fixin'! |
I think we need to bring up to date with master in order for some of the Linux builds to work. |
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.
Oh my C++ Unicode escapes are so hard to read. Suggestions added
#9761 had 4 failures, Windows x 2 were:
and macOS:
Developer build failure was codesigning fail. Will restart that one but it will probably fail on Core? |
Hm ok Thanks
El El mié, nov. 8, 2023 a la(s) 4:52 p.m., Marc Durdin <
***@***.***> escribió:
… #9761 <#9761> had 4 failures,
Windows x 2 were:
02:37:59 ../../../src/debuglog.cpp(467): error C2220: the following warning is treated as an error
02:37:59 ../../../src/debuglog.cpp(467): warning C4477: 'snprintf' : format string '%4.6X' requires an argument of type 'unsigned int', but variadic argument 1 has type 'char32_t'
https://build.palaso.org/buildConfiguration/KeymanDesktop_TestPullRequests/422546?buildTab=log&focusLine=2451&linesState=370&logView=flowAware
and macOS:
73/83 keyman_core:ldml-keyboards / k_008_transform_norm FAIL 0.06s killed by signal 6 SIGABRT
...
83/83 keyman_core:ldml / test_transforms FAIL 0.81s killed by signal 6 SIGABRT
https://build.palaso.org/buildConfiguration/Keyman_Common_KPAPI_TestPullRequests_macOS/422542?buildTab=log&focusLine=3094&linesState=89&logView=flowAware
Developer build failure was codesigning fail. Will restart that one but it
will probably fail on Core?
—
Reply to this email directly, view it on GitHub
<#9761 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGQZMZKE3TKK4U34BUD2ATYDQEMHAVCNFSM6AAAAAA57XCBZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBSHAZDOMZVGE>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
put in a patch |
@mcdurdin fail didn't seem to repro here, but it turns out: but
Seems like the status isn't being reported properly. So i'm getting false positives on my end. EDIT Whoa, "test failed with 0" … but, that ends up Hmm. |
@ermshiperete @mcdurdin |
…e/9468-marker-normalization-epic-ldml
I cleaned this up and moved the test-case-fix stuff into another PR |
- go back to NFD for the context, for now - anticipating when the privatecontext is NFD but the public context is NFC - also update the test cases For: #9468
- a little further - couple places where "it wasn't plugged in" - adding some LDML-TODOs - marker creep - fixed one unnecessary alloc/dealloc For: #9468
- test fix For: #9468
Keyman Core macOS build failed with:
|
doesn't repro locally, checking still |
- literally a bad assert. the error case is handled below, in fact the unit test tests for it. - for some reason, assert.h wasn't included in some cases locally. For: #9468
fixed, it was actually a bad assert. The case it was asserting for was handled in error checking code one line below. I had a local build environment that ended up ignoring the assert (which was a source bug also fixed)! |
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.
LGTM as far as it goes -- still more iterations needed on multiple markers between two chars I guess.
One issue possible with BT_UNKNOWN type backspaces -- it should only happen with an empty context.
core/tests/unit/ldml/ldml.cpp
Outdated
assert(context.back().character == ch); | ||
context.pop_back(); | ||
} else { | ||
assert(act.backspace.expected_type == KM_CORE_BT_UNKNOWN); // else it must be unknown |
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.
BT_UNKNOWN should only be used when the context is empty.
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.
added an assert for that request
might as well update. mac failure seemed to be timeout |
Changes in this pull request will be available for download in Keyman version 17.0.215-alpha |
For: #9468
@keymanapp-test-bot skip