-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Add tizen armel build CI for pull request #56281
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
Conversation
|
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
f2b2066 to
4156526
Compare
|
Currently, it fails before #55789 is merged. |
4156526 to
99a316b
Compare
|
Tagging subscribers to this area: @hoyosjs Issue DetailsWith ubuntu-18.04-cross-armel-tizen docker image,
|
99a316b to
72f1373
Compare
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.
Right. It needs a portable option and some others.
However, as I know, there is no ARMEL environment for test in the CI.
To prevent build failure, I just want to add Tizen ARMEL build this time.
Thank you.
|
@safern Could you review this PR? I added Tizen ARMEL Build and it works. However, I think I missed some details. Thank you. |
2d50683 to
1a03b2a
Compare
|
@safern I think errors are not related to this patch. Could you please review it? |
|
@safern Thank you! :) |
1a03b2a to
e00cba4
Compare
|
Oops. I pushed the old patch by mistake. Resolved now. |
|
This is currently just adding support for the |
54a6181 to
5259807
Compare
I think the others are handled by arm32 (hardfp) build. |
1f5fb96 to
afc7249
Compare
0317434 to
53f21c0
Compare
|
I think failures are not related to this PR. Could you please review and merge? |
|
@safern Could you please take final look and merge if it looks good? |
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.
Last question. It is currently showing up on the UI as Linux armel as the name, do we want it to be that or Tizen armel to make it more clear?
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 would be nice to have more distinct name for this (Tizen armel).
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.
Thank you for the review. I updated the name on the UI.
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.
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.
Could you please review it?
|
@clamp03 I see that there is an error on the build coreclr runtime step: Also, I see that in that step the distro rid is resolved as: I think we need to fix this? |
fac10bf to
49699d6
Compare
|
@safern Thank you for the review
Sorry. I missed error messages.
In our Tizen, we use clr and libs.native with portable build for tizen and the others for common linux-armel. |
49699d6 to
aef39e1
Compare
|
An error (multiline comment) in runtime/src/coreclr/jit/morph.cpp Lines 10914 to 10916 in 80e843f
@safern @jkotas Could you please review this PR and merge if it is good? |
|
I pushed a commit to fix gcc build in #60328 (period after trailing \ on single-line comment line is how we fixed issues in dotnet/coreclr in morph.cpp and other places). |
|
@hoyosjs @jkoritzinsky it seems like the GCC build is broken? |
|
It seems like that break was fixed on: #60333. |
|
Thanks, @clamp03 🎉 |
With ubuntu-18.04-cross-armel-tizen docker image,
check Tizen_armel build for each pull reqest.