You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains 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
The reason will be displayed to describe this comment to others. Learn more.
Oh, and I found the test timeout, that's a bad signal. Any ideas to reduce unit test time? Or separate integration test part to its own Action, then we can set a longer time for it.
The reason will be displayed to describe this comment to others. Learn more.
Oh, and I found the test timeout, that's a bad signal. Any ideas to reduce unit test time? Or separate integration test part to its own Action, then we can set a longer time for it.
We are running a lot of tests currently. Perhaps we could add a go test -short mode for regular development, and then use go test before releases? If you wish, feel free to look into updating the CI test actions. I think you are far more familiar with GitHub actions than I am @dannypsnl (with #142 and #144).
The reason will be displayed to describe this comment to others. Learn more.
BTW, I want to remove Go 1.12 test, the old version would contain more and more problems out of exception. Supporting it would take effort but we have limited human resource, and the lastest version already move to 1.15, I tend to maintain three versions only.
96af489
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 also link to document?
96af489
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.
Good idea.
96af489
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.
@dannypsnl would you do the commit adding a link to https://llir.github.io/document/?
96af489
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.
Sure
96af489
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.
Oh, and I found the test timeout, that's a bad signal. Any ideas to reduce unit test time? Or separate integration test part to its own Action, then we can set a longer time for it.
96af489
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.
We are running a lot of tests currently. Perhaps we could add a
go test -short
mode for regular development, and then usego test
before releases? If you wish, feel free to look into updating the CI test actions. I think you are far more familiar with GitHub actions than I am @dannypsnl (with #142 and #144).Cheers,
Robin
96af489
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.
Probably would be ok, maybe run a full check on PR, short check on commit? We can have several actions for different purposes.
96af489
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.
BTW, I want to remove Go 1.12 test, the old version would contain more and more problems out of exception. Supporting it would take effort but we have limited human resource, and the lastest version already move to 1.15, I tend to maintain three versions only.