Skip to content

[master] Update dependencies from dotnet/arcade #18461

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jan 23, 2020
Merged

[master] Update dependencies from dotnet/arcade #18461

merged 1 commit into from
Jan 23, 2020

Conversation

dotnet-maestro[bot]
Copy link
Contributor

This pull request updates the following dependencies

From https://github.com/dotnet/arcade

  • Subscription: a6dbb97b-1d09-43d1-e8f9-08d76e1cf1e0
  • Build: 20200118.1
  • Date Produced: 1/18/2020 1:38 PM
  • Commit: ebc71292545adda514c1e6a5657cd9ab753240bc
  • Branch: refs/heads/master
  • Updates:
    • Microsoft.DotNet.Arcade.Sdk -> 5.0.0-beta.20068.1
    • Microsoft.DotNet.GenAPI -> 5.0.0-beta.20068.1
    • Microsoft.DotNet.Helix.Sdk -> 5.0.0-beta.20068.1

@dotnet-maestro
Update dependencies from https://github.com/dotnet/arcade build 20200…
9bed5f8 
…118.1

- Microsoft.DotNet.Arcade.Sdk - 5.0.0-beta.20068.1
- Microsoft.DotNet.GenAPI - 5.0.0-beta.20068.1
- Microsoft.DotNet.Helix.Sdk - 5.0.0-beta.20068.1
@dotnet-maestro dotnet-maestro bot requested a review from dougbu as a code owner January 20, 2020 13:05
@ghost ghost added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Jan 20, 2020
@dotnet-maestro
Copy link
Contributor Author

dotnet-maestro bot commented Jan 20, 2020 •
edited
Loading

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

  • ❌ Standard Merge Policies Unsuccessful checks: aspnetcore-ci, aspnetcore-ci (Build Test: macOS 10.13), aspnetcore-ci (Build Test: Windows Server 2016 x64)
  • ✔️ Standard Merge Policies Succeeded - No reviews have requested changes.

@JunTaoLuo
Copy link
Contributor

JunTaoLuo commented Jan 23, 2020 •
edited
Loading

@MattGal is there a known issue with AzDO when cloning a repo? We are seeing errors like:

git checkout --progress --force be44154d206c0b1579ee64d1cb770ba7ea48cde4
fatal: reference is not a tree: be44154d206c0b1579ee64d1cb770ba7ea48cde4
##[error]Git checkout failed with exit code: 128

https://dev.azure.com/dnceng/public/_build/results?buildId=490411&view=logs&jobId=c18bc5be-c9c3-5147-7bbf-cfe43d8b0016&j=c18bc5be-c9c3-5147-7bbf-cfe43d8b0016&t=3dd0ff83-b32a-5036-3dff-f1003b67980e

@dotnet-maestro
Copy link
Contributor Author

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

  • ❌ Standard Merge Policies Unsuccessful checks: aspnetcore-ci, aspnetcore-ci (Build Test: macOS 10.13), aspnetcore-ci (Build Test: Windows Server 2016 x64)
  • ✔️ Standard Merge Policies Succeeded - No reviews have requested changes.

@JunTaoLuo
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@dotnet-maestro
Copy link
Contributor Author

dotnet-maestro bot commented Jan 23, 2020 •
edited
Loading

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

  • ❓ Waiting on checks: aspnetcore-ci, aspnetcore-ci (Build Tests: Helix x64), aspnetcore-ci (Build Test: Ubuntu 16.04 x64), aspnetcore-ci (Build Test: Templates - Windows Server 2016 x64), aspnetcore-ci (Build Test: macOS 10.13), aspnetcore-ci (Build Test: Windows Server 2016 x64), aspnetcore-ci (Build Build: Windows x64/x86)
  • ✔️ Standard Merge Policies Succeeded - No reviews have requested changes.

@MattGal
Copy link
Member

MattGal commented Jan 23, 2020

@MattGal is there a known issue with AzDO when cloning a repo? We are seeing errors like:

git checkout --progress --force be44154d206c0b1579ee64d1cb770ba7ea48cde4
fatal: reference is not a tree: be44154d206c0b1579ee64d1cb770ba7ea48cde4
##[error]Git checkout failed with exit code: 128

https://dev.azure.com/dnceng/public/_build/results?buildId=490411&view=logs&jobId=c18bc5be-c9c3-5147-7bbf-cfe43d8b0016&j=c18bc5be-c9c3-5147-7bbf-cfe43d8b0016&t=3dd0ff83-b32a-5036-3dff-f1003b67980e

There definitely is! Tracked by https://icm.ad.msft.net/imp/v3/incidents/details/171862607/home . I'm sitting on the bridge for it right now. Only mitigation from your side would be somehow to coordinate such that folks don't perform merges during the provisioning phase of a build (not really feasible). I'll share the IcM with the partners alias as this seems to be more widespread than I thought.

@dotnet-maestro
Copy link
Contributor Author

dotnet-maestro bot commented Jan 23, 2020 •
edited
Loading

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

  • ❓ Waiting on checks: aspnetcore-ci, aspnetcore-ci (Build Test: Templates - Windows Server 2016 x64)
  • ✔️ Standard Merge Policies Succeeded - No reviews have requested changes.

@JunTaoLuo
Copy link
Contributor

Luckily it worked on a rerun.

@JunTaoLuo JunTaoLuo merged commit a49e084 into master Jan 23, 2020
@JunTaoLuo JunTaoLuo deleted the darc-master-a177af24-9fbe-4a60-8b44-d222d6ae0966 branch January 23, 2020 01:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dougbu dougbu Awaiting requested review from dougbu

Assignees
No one assigned
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@JunTaoLuo @MattGal