-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Conversation
@dotnet-bot test CI please |
@dotnet-bot test Linux x64 Release Build |
@gbalykov Is there anything else you need to do here before we think about merging? |
@wtgodbe we need to wait for dotnet/coreclr#19058 to get to sdk first, because build with tizen.5.0.0 RID doesn't work yet |
@gbalykov any update? |
@wtgodbe release/2.1 Tizen builds should work now, but master builds do not work yet, this is work in progress |
This reverts commit 37774fd.
* Update arm32_ci_script.sh * Update arm32_ci_script.sh * Update arm32_ci_script.sh
* Update Tizen RID for CI * Update Tizen url for rootfs generation
@dotnet-bot test ci please |
@dotnet-bot test OSX x64 Debug Build |
@dotnet-bot test ci please |
@gbalykov, is this still blocked? From your comment almost a month ago it sounds like this can now be merged? |
@stephentoub this should work now, but I was not able to test Tizen CI on this PR, as |
@dotnet-bot test ci please |
@stephentoub tizen jobs are not regenerated, do you know what could be the reason of this? |
@mmitche? Do we not regenerate jobs as part of part of asking to test ci please? I remember that used to be the case, and you had to actually merge and then subsequent PRs would pick it up, but I thought that changed. No? |
@stephentoub It still only generates disabled jobs for verification, it does not do anything to the jobs on this PR. That will change as we move to Azure DevOps. |
@stephentoub for some reason |
@dotnet-bot test Tizen armel Release Build |
@dotnet-bot test OSX x64 Debug Build please |
2 similar comments
@dotnet-bot test OSX x64 Debug Build please |
@dotnet-bot test OSX x64 Debug Build please |
@stephentoub CI testing has fully passed |
@danmosemsft, can this be merged? (release/2.1) |
Merged to match dotnet/coreclr#19410 per discussion. |
Approved |
cc @alpencolt