-
Notifications
You must be signed in to change notification settings - Fork 378
Comparing changes
Open a pull request
base repository: dotnet/arcade
base: 19e7e76
head repository: dotnet/arcade
compare: 72b28b7
- 7 commits
- 9 files changed
- 4 contributors
Commits on Oct 30, 2020
-
Update dependencies from https://github.com/dotnet/xliff-tasks build …
…20201029.1 (#6494) [master] Update dependencies from dotnet/xliff-tasks
Configuration menu - View commit details
-
Copy full SHA for 66a7dc1 - Browse repository at this point
Copy the full SHA 66a7dc1View commit details -
Update dependencies from https://github.com/dotnet/xharness build 202…
…01030.1 (#6495) [master] Update dependencies from dotnet/xharness
Configuration menu - View commit details
-
Copy full SHA for cd9ceb5 - Browse repository at this point
Copy the full SHA cd9ceb5View commit details
Commits on Nov 2, 2020
-
[master] Update dependencies from dotnet/xharness dotnet/arcade dotne…
…t/xliff-tasks dnceng/internal/dotnet-symuploader (#6498) [master] Update dependencies from dotnet/xharness dotnet/arcade dotnet/xliff-tasks dnceng/internal/dotnet-symuploader
Configuration menu - View commit details
-
Copy full SHA for 33c97d6 - Browse repository at this point
Copy the full SHA 33c97d6View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2f9114e - Browse repository at this point
Copy the full SHA 2f9114eView commit details -
Fix asynchronous nuget push and other bugs (#6500)
- Somehow the async nuget push got lost at some point. This resolves this by asynchronously waiting for process exit. - Fixes an issue where we would log the output of all nuget failures even in non-failure cases, if another failure happened. The primary case for this is if a package push fails, but the file on the feed is the same as what we are pushing. This is not an error case, but if another operation in publishing fails, we'll erroneously log it. - Fixes an issue where we would not log a package as succcesfully pushed if there was another error in publishing.
Configuration menu - View commit details
-
Copy full SHA for b0d840c - Browse repository at this point
Copy the full SHA b0d840cView commit details -
Make XHarness CLI test fail the build (#6503)
This steps was failing because one of the machines didn't have `xcode-select` pointing to the Xcode installation but to the Xcode command line tools. That's why it only failed occasionally when it hit this one machine. The step should fail the build and is stable otherwise. Resolves dotnet/xharness#337 Error message improved here dotnet/xharness#349
Configuration menu - View commit details
-
Copy full SHA for 80b92f2 - Browse repository at this point
Copy the full SHA 80b92f2View commit details -
Configuration menu - View commit details
-
Copy full SHA for 72b28b7 - Browse repository at this point
Copy the full SHA 72b28b7View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 19e7e76...72b28b7