Update Tizen CI docker image#17814
Conversation
|
@dotnet-bot test Tizen armel Cross Release Build |
|
@dotnet-bot test OSX10.12 x64 Checked Innerloop Build and Test |
|
@jkotas could we reenable Tizen in default CI now? |
|
|
@gbalykov Does this also address QEMU issues like #6298? If not, I suspect we won't be able to tolerate the spurious failures in the default CI jobs. If you aren't sure, we can do a trial run, on the condition that if the spurious failures return, we disable again. |
|
Docker image now has newer version of QEMU. I've ran Tizen tests on this PR and there seems to be no problem with them. I agree with your idea to disable tests if spurious failures return. I'll update this PR with enabled Tizen CI in default jobs and open same PR for corefx/core-setup. |
|
@dotnet-bot test this please |
d655ff1 to
75c4051
Compare
|
@dotnet-bot test Tizen armel Cross Release Build |
|
@dotnet-bot test this please |
a4386dd to
16a64fd
Compare
|
@dotnet-bot test Tizen armel Cross Release Build |
|
@RussKeldorph, could you, please, take a look? |
| ] | ||
| ], | ||
| 'Tizen': [ | ||
| 'armem': [ |
There was a problem hiding this comment.
@gbalykov should this be "armel" instead of "armem"?
There was a problem hiding this comment.
Ah, ok, thank you for the clarification!
|
@dotnet-bot test ci please |
16a64fd to
8dc93e4
Compare
|
@dotnet-bot test ci please |
|
@dotnet-bot test Tizen armel Cross Release Build |
|
@janvorli, I've fully reverted commit, which disabled Tizen CI, so now "test ci please" should work. However, it seems that I can't run it. Could you, please, rerun it? |
|
@dotnet-bot test ci please |
|
@janvorli Thank you! |
Based on "Update Tizen CI docker image (dotnet#17814)".
Update Tizen CI docker image to ubuntu 16.04
This seems to fix #17028. Related issue (https://github.com/dotnet/corefx/issues/28901)
cc @Dmitri-Botcharnikov @alpencolt