[Storage] Figure out what to do with long-running tests

[seanmcc-msft]

Long running unit tests timeout in Pipelines, and take too long to run every time locally. We should find a solution for managing these tests.

[kasobol-msft]

One remaining test is

azure-sdk-for-net/sdk/storage/Azure.Storage.Files.DataLake/tests/DataLakePartitionedUploaderTests.cs

Lines 223 to 255 in 5b7afe2

	[Test]
	[Explicit]
	[Ignore("https://github.com/Azure/azure-sdk-for-net/issues/12312")]
	public async Task CanHandleLongAppendBufferedUpload()
	{
	const long blockSize = int.MaxValue + 1024L;
	const int numBlocks = 2;
	Stream content = new Storage.Tests.Shared.PredictableStream(numBlocks * blockSize);
	TrackingArrayPool testPool = new TrackingArrayPool();
	AppendSink sink = new AppendSink(false); // sink can't hold long blocks, and we don't need to look at their data anyway.
	Mock<DataLakeFileClient> clientMock = new Mock<DataLakeFileClient>(MockBehavior.Strict, new Uri("http://mock"), new DataLakeClientOptions());
	clientMock.SetupGet(c => c.ClientConfiguration.ClientDiagnostics).CallBase();
	clientMock.SetupGet(c => c.ClientConfiguration.Version).CallBase();
	SetupInternalStaging(clientMock, sink);
	var uploader = new PartitionedUploader<DataLakeFileUploadOptions, PathInfo>(
	DataLakeFileClient.GetPartitionedUploaderBehaviors(clientMock.Object),
	new StorageTransferOptions
	{
	InitialTransferSize = 1, // forces buffered upload
	MaximumTransferSize = blockSize,
	MaximumConcurrency = 2
	},
	arrayPool: testPool);
	Response<PathInfo> info = await InvokeUploadAsync(uploader, content);
	Assert.AreEqual(s_response, info);
	foreach (var block in sink.Appended.Values)
	{
	Assert.AreEqual(blockSize, block.Length);
	}
	}

. afaik azurite doesn't have DFS apis, but on the other hand dfs endpoint will go away and datalake sdk will talk to blob endpoint some day for this scenario.

[JimSuplizio]

Hi @seanmcc-msft, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.