-
Notifications
You must be signed in to change notification settings - Fork 524
Refactor code generation verification #2108
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
Changes from all commits
cdbdb47
c464d56
4cb51fd
ba4487c
3a5e182
ef32b2f
7a28526
3a7d29e
0f208f2
5428faf
ea808a3
50966e3
2c4c863
ca1c7ef
ed770bf
f8f6014
6cf5409
3e3a9bf
4c00cb8
ebbacc8
4627280
0b2a51c
73a6060
aca46e0
03b369e
37043a5
8f4d4e6
6d733f1
df81c08
f1561da
8b20c95
d792074
9c6c511
79a17e6
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -421,6 +421,8 @@ func TestServiceFetchBlocksMalformed(t *testing.T) { | |
| } | ||
|
|
||
| func TestOnSwitchToUnSupportedProtocol(t *testing.T) { | ||
| t.Skip("This test is flacky and need to be fixed.") | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we have a ticket to follow up on this?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I will create a follow up ticket for this one, once this PR is approved and merged in.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There are a bunch of these, I think there's an umbrella ticket to fix:
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yes, I'm aware of that.. The important thing is that we need to keep tracking these explicitly so that we won't forget these. |
||
|
|
||
| // Test the interruption in the initial loop | ||
| // This cannot happen in practice, but is used to test the code. | ||
| { | ||
|
|
||
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.
Will it be useful to add a cleanall option which includes generated_files?
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 don't think so. That would cause more issues, since cleaning them without regenerating them would cause build failures ( keep in mind that I've removed the dependencies on these, since they're alway there ).
That's the reason I added
rebuild_swaggertarget.