-
Notifications
You must be signed in to change notification settings - Fork 129
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
testing(dot): migrate dot/sync tests to integration tests #2116
Conversation
Codecov Report
@@ Coverage Diff @@
## development #2116 +/- ##
===============================================
- Coverage 61.32% 57.39% -3.94%
===============================================
Files 216 216
Lines 28403 28493 +90
===============================================
- Hits 17418 16353 -1065
- Misses 9198 10456 +1258
+ Partials 1787 1684 -103
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
@edwardmack didn't git detect the file movements ('replace')? If you didn't modify the files much, git should had detected these are just file movements, drastically reducing deltas (correct me if I'm wrong though). EDIT: you might have to remove i.e. |
2b46760
to
bdee8ea
Compare
Also sorry to be the git maniac here, but perhaps you could interactively rebase on your first commit to have the following commits:
And then merge commits instead of squash and merge? That way file movements will be kept in history and easier to merge/rebase on for other branches (and also for git blame etc.). Otherwise git might just think it's purely new files and older files got deleted. I can help with that let me know 😉 |
324c1f6
to
b6073f0
Compare
@qdm12 I've interactively rebased these commits, it seems to be clearer now. Please take a look again and let me know your thoughts. |
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.
Nice rebase! Just a few questions and suggestions to revert back to how it was to reduce deltas.
We should be able to squash and merge and git will track file movements correctly, so don't worry about adding commits 😉
@@ -647,7 +650,6 @@ func TestChainSync_doSync(t *testing.T) { | |||
resp := &network.BlockResponseMessage{ | |||
BlockData: []*types.BlockData{ | |||
{ | |||
Hash: common.Hash{0x1}, |
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.
Are we sure about these removals? Does the test pass locally?
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.
I've re-tested, and I have re-added these. I'm not sure why I removed these.
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.
Can you squash the last few commits in the 2nd commit, and then let's rebase and merge
Note in the future, you can stage your changes and then do git commit --amend && git push --force
to bundle changes in the last commit.
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.
Ignore the comment above; changes are minimal so the squash and merge should track file movements properly. Let's just squash and merge it 💯
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.
Please add dot/sync
to
github.com/ChainSafe/gossamer/lib/babe, |
Added |
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.
Just a few comments
- Make sure to not modify irrelevant code.
- Move back the line spacing that was removed.
TestChainProcessor_HandleJustification
fails. If CI keeps timing out, run relevant integration tests locally and confirm if they pass.
@kishansagathiya I've addressed PR comments, please re-review and let me know if any issues remain. |
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.
🎉
remove empty files that were moved to xx_integration_tests
fix lint issues address PR comments re-add deleted code fix TestWorkerToRequest and re-add TestChainSync_highestBlock
f9bf802
to
6880a9b
Compare
Changes
xx_integration_test.go
Tests
Issues
Primary Reviewer