Skip to content
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.

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

[release/3.0] Update dependencies from dotnet/arcade #6938

Conversation

dotnet-maestro[bot]
Copy link
Contributor

@dotnet-maestro dotnet-maestro bot commented Jan 4, 2024

This pull request updates the following dependencies

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

  • Subscription: 45c6fd49-3a4f-4675-f3da-08dc0c527e17
  • Build: 20231220.2
  • Date Produced: December 20, 2023 12:15:53 PM UTC
  • Commit: 84129325171e65373edef24019e1171feeb19cbc
  • Branch: refs/heads/release/8.0
  • Updates to .NET SDKs:
    • Updates tools.dotnet to 8.0.100

…220.2

Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.SwaggerGenerator.MSBuild , Microsoft.DotNet.XUnitExtensions
 From Version 8.0.0-beta.23265.1 -> To Version 8.0.0-beta.23620.2
@ericstj ericstj self-assigned this Jan 4, 2024
@ericstj
Copy link
Member

ericstj commented Jan 4, 2024

We need to port changes from #6703 and #6935 here.

Copy link

codecov bot commented Jan 4, 2024

Codecov Report

Attention: 44 lines in your changes are missing coverage. Please review.

Comparison is base (d96d7b7) 68.81% compared to head (df6f817) 68.80%.

Additional details and impacted files
@@               Coverage Diff               @@
##           release/3.0    #6938      +/-   ##
===============================================
- Coverage        68.81%   68.80%   -0.01%     
===============================================
  Files             1240     1240              
  Lines           249397   249400       +3     
  Branches         25496    25494       -2     
===============================================
- Hits            171614   171610       -4     
- Misses           71189    71196       +7     
  Partials          6594     6594              
Flag Coverage Δ
Debug 68.80% <82.32%> (-0.01%) ⬇️
production 63.26% <75.00%> (-0.01%) ⬇️
test 88.49% <82.44%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
...osoft.Data.Analysis.Tests/ArrowIntegrationTests.cs 100.00% <100.00%> (ø)
...icrosoft.Data.Analysis.Tests/DataFrameJoinTests.cs 100.00% <100.00%> (ø)
.../Microsoft.ML.AutoML.Tests/ColumnInferenceTests.cs 96.29% <100.00%> (ø)
...t.ML.AutoML.Tests/SuggestedPipelineBuilderTests.cs 100.00% <100.00%> (ø)
...crosoft.ML.Core.Tests/UnitTests/TestEntryPoints.cs 98.45% <100.00%> (ø)
test/Microsoft.ML.Core.Tests/UnitTests/TestLoss.cs 100.00% <100.00%> (ø)
...t/Microsoft.ML.Core.Tests/UnitTests/TestVBuffer.cs 95.31% <100.00%> (ø)
test/Microsoft.ML.CpuMath.UnitTests/UnitTests.cs 95.70% <100.00%> (ø)
test/Microsoft.ML.FSharp.Tests/SmokeTests.fs 87.23% <ø> (ø)
test/Microsoft.ML.Fairlearn.Tests/MetricTest.cs 100.00% <100.00%> (ø)
... and 30 more

... and 6 files with indirect coverage changes

michaelgsharp and others added 17 commits January 5, 2024 10:12
Asserting on `_rowCount <  Utils.Size(_valueBoundaries)` was catching a
case where `_rowCount`'s update was reordered before `_valueBoundaries`

This was unnecessary, since this method doesn't need to use `_rowCount`.

Instead, make the asserts use only `idx` which will be maintained
consistent with the waiter logic in this cache.
�Ensure we only ever use `_rowCount` from the caching thread, so write
reordering won't matter.
* Don't include the SDK in our helix payload

I noticed that the tests included the latest SDK - including the host -
in our helix payloads.

This is a large amount of unnecessary downloads and it also makes it so
we use the latest host on the older frameworks which can fail when the
latest host drops support for distros.

Since our tests shouldn't need the full CLI, remove this from our helix
payloads.

We'll instead get just the runtime we need through `AdditionalDotNetPackage`

* Place Helix downloaded runtime on the PATH

Helix only sets the path when the CLI is included, however we don't
need the CLI.
…6923)

Precision might cause small differences to round to a different number.
Instead compare with a tolerance which is not sensitive to rounding.
@ericstj
Copy link
Member

ericstj commented Jan 5, 2024

For testing we also need
#6924
#6918
#6923

@ericstj
Copy link
Member

ericstj commented Jan 5, 2024

We may want to "merge" commit on this one to preserve distinct history. I can rebase to combine all the small changes from the previous arcade PR to clean things up. Will do that after I see the build passing for auditing purposes (making sure I got every relevant commit).

@ericstj
Copy link
Member

ericstj commented Jan 5, 2024

Hmm, a couple unique failures here. On Ubuntu:

Finished test: Microsoft.ML.Scenarios.TensorFlowScenariosTests.TensorFlowTransformInputOutputTypesTest with memory usage 2,374,266,880.00
Starting test: Microsoft.ML.Tests.NerTests.TestSimpleNer
Finished test: Microsoft.ML.Tests.NerTests.TestSimpleNer with memory usage 1,505,148,928.00
Starting test: Microsoft.ML.Tests.ObjectDetectionTests.SimpleObjDetectionTest
total : 171, filtered: 0, filter ratio: 0.000%
Finished test: Microsoft.ML.Tests.ObjectDetectionTests.SimpleObjDetectionTest with memory usage 1,648,238,592.00
Starting test: Microsoft.ML.Tests.QATests.TestSimpleQA
Killed
+ export _commandExitCode=137

Maybe OOM killer? Though memory went down from previous tests, not sure how much is needed for QA.

Coverage build failed SdcaLogisticRegression test with Assert.InRange() Failure: Value not in range\r\nRange: (0 - 0.5)\r\nActual: 0.51672692765628392
https://dev.azure.com/dnceng-public/public/_build/results?buildId=516419&view=ms.vss-test-web.build-test-results-tab&runId=12113782&resultId=101543

Both of these seem unrelated to this change, but curious for your thoughts @michaelgsharp

@ericstj
Copy link
Member

ericstj commented Jan 8, 2024

Seems like those were flaky. This is ready for review @michaelgsharp

@ericstj ericstj added the ** NO MERGE ** Testing PR only, do not merge label Jan 8, 2024
@ericstj
Copy link
Member

ericstj commented Jan 9, 2024

@michaelgsharp this is still waiting on your review, please 🙏

@michaelgsharp michaelgsharp merged commit f602581 into release/3.0 Jan 9, 2024
25 checks passed
@dotnet-maestro dotnet-maestro bot deleted the darc-release/3.0-a2cf7474-cd86-4a84-9585-d4f1d0edebcf branch January 9, 2024 17:08
@github-actions github-actions bot locked and limited conversation to collaborators Feb 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
** NO MERGE ** Testing PR only, do not merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants