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

Azurite fails to start in tests runs #17410

Closed
pakrym opened this issue Dec 8, 2020 · 3 comments · Fixed by #17430
Closed

Azurite fails to start in tests runs #17410

pakrym opened this issue Dec 8, 2020 · 3 comments · Fixed by #17430
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files) test-reliability Issue that causes tests to be unreliable

Comments

@pakrym
Copy link
Contributor

pakrym commented Dec 8, 2020

Still happening https://dev.azure.com/azure-sdk/public/_build/results?buildId=646247&view=logs&j=9cfc3b0b-53b1-524f-85ed-0ef4880bef82&t=277ae693-9b68-5ef5-d666-bb5a558e8cc2

   OneTimeSetUp: System.InvalidOperationException : 
Could not run Azurite based test due to: azurite process could not start with following output:

and error:
.
Make sure that:
- NodeJS is installed and available in $PATH (i.e. 'node' command can be run in terminal)
- Azurite V3 is installed via NPM (see https://github.com/Azure/Azurite for instructions)
- AZURE_AZURITE_LOCATION envorinment is set and pointing to location of directory that has 'azurite' command (i.e. run 'where azurite' in Windows CMD)



cc @kasobol-msft

@pakrym pakrym added Storage Storage Service (Queues, Blobs, Files) Client This issue points to a problem in the data-plane of the library. test-reliability Issue that causes tests to be unreliable labels Dec 8, 2020
@kasobol-msft kasobol-msft self-assigned this Dec 8, 2020
@kasobol-msft
Copy link
Contributor

The absence of output made me find this dotnet/runtime#18789 and plenty of similar posts on stackoverflow and other places. Then I found this dotnet/runtime#28025 .
Maybe we're using .netcore version that still has these problems.

As a workaround - instead of using these events I could spin out a Thread that reads from process.StandardInput directly. @pakrym what do you think?

@pakrym
Copy link
Contributor Author

pakrym commented Dec 8, 2020

We are waiting 15 seconds before firing the exception. Should be plenty for stdout to flush. https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/storage/Microsoft.Azure.WebJobs.Extensions.Storage.Common/tests/AzuriteFixture.cs#L123

@kasobol-msft
Copy link
Contributor

I hope this will yield more answers #17419

openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-net that referenced this issue Jan 22, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Mar 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files) test-reliability Issue that causes tests to be unreliable
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants