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

Update JitTrace files (#9752) #9756

Merged
merged 1 commit into from
Jan 2, 2024
Merged

Update JitTrace files (#9752) #9756

merged 1 commit into from
Jan 2, 2024

Conversation

v-smanchem
Copy link
Contributor

@v-smanchem v-smanchem commented Jan 2, 2024

Updating the Linux and Windows JIT trace files for Dev in anticipation of the next v4 release (4.29.0)

Windows

Function Initial Final Difference
DotNet 62 ms 8 ms 54 ms
Node 401 ms 14 ms 387 ms
DotNet-Isolated 417 ms 42 ms 375 ms

Linux

Total lines in latest windows jittracefile = 4667
Total lines in current jittracefile = 8217
Total lines in new jittracefile = 490
490 duplicates were skipped
Total lines in updated jittracefile = 8201

Pull request checklist

  • My changes do not require documentation changes
    • Otherwise: Documentation issue linked to PR
  • My changes should not be added to the release notes for the next release
    • Otherwise: I've added my notes to release_notes.md
  • My changes do not need to be backported to a previous version
    • Otherwise: Backport tracked by issue/PR #issue_or_pr
  • My changes do not require diagnostic events changes
    • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
  • I have added all required tests (Unit tests, E2E tests)

Additional information

Additional PR information

@v-smanchem v-smanchem merged commit aae3d33 into release/4.x Jan 2, 2024
6 checks passed
@v-smanchem v-smanchem deleted the JitTracePRv4.29.0 branch January 2, 2024 17:30
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.

None yet

2 participants