-
-
Notifications
You must be signed in to change notification settings - Fork 43
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(build): use cldr.version for cldr #345
Conversation
f692cc3
to
934cea9
Compare
934cea9
to
f43c1e4
Compare
yes i will propagate this to other workflows once its…working |
d35eb36
to
387c470
Compare
- name: Set up JDK 11 | ||
uses: actions/setup-java@v1 | ||
with: | ||
java-version: 11 | ||
- uses: actions/checkout@v2 |
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.
yes, it was checking out the repo twice!
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.
probably a merge conflict
0bc2502
to
d97f06d
Compare
so a major issue here is that github checkout, following security best practices, no longer handles the short hash to CLDR - actions/checkout#265 so the short hash such as 273d736f11 in 0.0.0-SNAPSHOT-273d736f11 is a challenge to checkout. I'm going back to an older version of the action, but it will be a stopgap. |
ed394ea
to
f0059e7
Compare
well this turned out to be kind of a mess… see if the caching helps at all. |
5a38bf2
to
0594323
Compare
@echeran remainng build errors seem unrelated - ideas? |
with: | ||
repository: unicode-org/cldr | ||
path: cldr | ||
ref: main |
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.
Alternatively, you can try using CLDR_REF
here instead of main
.
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.
doesn't work because it's not a full hash.
I think the second That seems like the only thing that is failing, so hopefully that is the fix needed to get this PR ready to merge. |
That was in the out-of-source, but the in-source was failing tests also. |
- github action should use the cldr.version for checkout - checkout all of CLDR (!) and then switch to the CLDR_REF Fixes unicode-org#316 Co-authored-by: Elango Cheran <elango@unicode.org>
- Add -DfailIfNoTests=false to the retry-confusables call
8c8cb5e
to
049488e
Compare
OK, spot the problem with in-source build: $ mkdir cldr
$ ln -s cldr ..
$ cd ../cldr … fixed |
- actions were failing, and a new install of flake8 locally broke for me as well Ref: https://stackoverflow.com/a/74558566/185799
ignore = E302, | ||
# expected 2 blank lines, found 1 | ||
E701, | ||
# multiple statements on one line | ||
W504, | ||
# line break after binary operator |
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.
Unrelated deps based break
Broken:
https://github.com/unicode-org/unicodetools/actions/runs/3576355216/jobs/6014061731
Bad err message… debugged it to find the failing issue
came across
from a few days ago
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.
This has been biting tons of Python devs who use flake8 for linting. Inline comments have always been "wrong", they're just enforcing it now :-)
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.
a better error message would have been nice…
And yes, it's open source and i haven't opened a PR yet.
@echeran @markusicu in-source and python are passing again. out of source is getting much further. PTAL Also rebased. |
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. Thanks!
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.
looks... eminently plausible. thank you very much for getting this to work!
Fixes #316