Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: dotnet/arcade
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 19e7e76
Choose a base ref
...
head repository: dotnet/arcade
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 72b28b7
Choose a head ref
  • 7 commits
  • 9 files changed
  • 4 contributors

Commits on Oct 30, 2020

  1. Configuration menu
    Copy the full SHA
    66a7dc1 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    cd9ceb5 View commit details
    Browse the repository at this point in the history

Commits on Nov 2, 2020

  1. [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
    dotnet-maestro[bot] authored Nov 2, 2020
    Configuration menu
    Copy the full SHA
    33c97d6 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    2f9114e View commit details
    Browse the repository at this point in the history
  3. 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.
    mmitche authored Nov 2, 2020
    Configuration menu
    Copy the full SHA
    b0d840c View commit details
    Browse the repository at this point in the history
  4. 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
    premun authored Nov 2, 2020
    Configuration menu
    Copy the full SHA
    80b92f2 View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    72b28b7 View commit details
    Browse the repository at this point in the history
Loading