-
Notifications
You must be signed in to change notification settings - Fork 2k
Migrate core test to insta, part1 #16324
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
Merged
blaginin
merged 7 commits into
apache:main
from
Chen-Yuan-Lai:migrate_core_test_to_insta
Jun 17, 2025
Merged
Changes from 1 commit
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
a88b86d
feat: migrate core test into insta
0f719c2
feat: enhance tests with snapshot assertions and remove unused macros
c8dd007
feat: rewrite snapshot test in explain_analyze_baseline_metrics
4a6ac4a
fix: update snapshot test to normalize file paths in explain_analyze_…
e95ed80
refactor: simplify snapshot assertions by removing format calls in op…
c981e70
feat: revert the original usage of assert_metrics macro in explain_a…
ef81186
Merge branch 'main' into migrate_core_test_to_insta
blaginin File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
feat: rewrite snapshot test in explain_analyze_baseline_metrics
- Loading branch information
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[µmn]- I think this can be somewhat flaky it the test takes more time - maybe match on[]?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree, current pattern can't match the longer time (ex. min, h, d). However, a broader pattern might match irrelevant strings. For example, match on
[ ]: metrics=[output_rows=1, elapsed_compute=110.947µs] -> metrics=[TIME]I'm currently considering to add more time units in the regex pattern:
Or, do you have any suggestions for a more precise way to match time-related strings? many thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe just for this teset case we could avoid using
instaand use the previous approach of substring matchesWhile that approach is also non ideal, it has seemed to work this far
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Happy with keeping as is, but on this
you can probably use lookahead https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Regular_expressions/Lookahead_assertion
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately, Rust's regex crate does not support lookahead or lookbehind assertions 😢 ( ref )