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

fix(tracing): avoid clashing network file names #22126

Merged
merged 1 commit into from
Apr 1, 2023

Conversation

dgozman
Copy link
Contributor

@dgozman dgozman commented Mar 31, 2023

With two contexts in the same test, we can get:

  • <testId>.network and <testId>-1.network files;
  • for export, we can copy <testId>.network into <testId>-1.network and try to copy into a file when another trace is reading from it.

Fixes #22089.

With two contexts in the same test, we can get:
- `<testId>.network` and `<testId>-1.network` files;
- for export, we can copy `<testId>.network` into `<testId>-1.network`
  and try to copy into a file when another trace is reading from it.
@dgozman dgozman force-pushed the fix-tracing-clashing-network branch from c72fc2a to 9ddeb04 Compare March 31, 2023 22:13
@dgozman dgozman merged commit 41e3e6d into microsoft:main Apr 1, 2023
20 checks passed
dgozman added a commit that referenced this pull request Apr 1, 2023
With two contexts in the same test, we can get:
- `<testId>.network` and `<testId>-1.network` files;
- for export, we can copy `<testId>.network` into `<testId>-1.network`
and try to copy into a file when another trace is reading from it.

Fixes #22089.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[REGRESSION]: Tests failing with "Error: tracing.stopChunk"
2 participants