Stabilize Azure Functions Durable E2E tests - #238
Merged
berndverst merged 1 commit intoJul 29, 2026
Conversation
Keep history export output outside the watched Function app and quarantine Azurite-dependent delayed visibility tests. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: cb2d68a5-0184-45af-bb9c-4def2afe8e8a
Contributor
There was a problem hiding this comment.
Pull request overview
This PR stabilizes the Azure Functions Durable E2E test suite by preventing Functions host restarts during history export and quarantining a small set of flaky Azurite-dependent scenarios.
Changes:
- Write history-export artifacts to an OS temp directory (outside the Function app root) to avoid triggering the Functions file watcher.
- Quarantine the Azurite “delayed visibility” dependent E2Es via a centralized skip marker with a linked tracking issue.
- Apply the shared marker across the affected V1, durabletask, entity, and scheduled-task E2E tests.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| tests/azure-functions-durable/e2e/test_v1_patterns_e2e.py | Skips the V1 timer E2E affected by Azurite delayed-visibility flakiness. |
| tests/azure-functions-durable/e2e/test_dtask_scheduled_e2e.py | Skips scheduled-task E2Es that depend on delayed queue message visibility. |
| tests/azure-functions-durable/e2e/test_dtask_patterns_e2e.py | Skips the durabletask-native timer E2E affected by delayed visibility. |
| tests/azure-functions-durable/e2e/test_dtask_entities_advanced_e2e.py | Skips delayed entity signal E2Es impacted by Azurite behavior. |
| tests/azure-functions-durable/e2e/apps/dtask_style/history_export_routes.py | Moves exported history output to a stable temp directory outside the app to prevent host restarts. |
| tests/azure-functions-durable/e2e/_markers.py | Adds a centralized, documented pytest skip marker for the Azurite delayed-visibility quarantine. |
berndverst
approved these changes
Jul 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The AzureStorage polling interval does not address this failure: the failed runs polled after the messages were due, but Azurite returned empty queue responses. Retry-policy E2Es remain enabled because they have not exhibited the failure and use substantially shorter delays.
Validation
python -m flake8on the changed E2E files