-
Notifications
You must be signed in to change notification settings - Fork 38
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
Testament - implement --retry and fix --failing #96
Conversation
shayanhabibi
commented
Dec 6, 2021
•
edited
Loading
edited
- Documentation
- Make easier to maintain and better file structure
- Make --failing also filter stdout
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.
Suggested a few things.
Your code is so much better. 😭 Ok so, is shrink it to get your retry bits in and maybe have a draft for the additional changes. Imma take a crack at "testament2" this weekend. Basically spec parsing only, shrink the category madness, and ditch megatest. Should give a much cleaner base to work with... seriously. |
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.
Non-blockers, just noticed something.
testament/specs.nim
Outdated
@@ -265,6 +273,10 @@ proc isCurrentBatch*(testamentData: TestamentData; filename: string): bool = | |||
|
|||
proc parseSpec*(filename: string): TSpec = | |||
result.file = filename | |||
if retryContainer.retry and retryContainer.names.anyIt(it in result.file): |
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.
So here is an idea, that you'll love.... Ok maybe love is a strong word, but if it's possible to store the full log, we could see which tests are newly discovered and need to be run, or only store successes?
So some failures, add tests, retry runs failure and new.
I like this. Can add this after; I just really want to be able to use the failing/retry when working with other branches from devel. |
d064676
to
71fca8e
Compare
I am happy with the current implementation of --failing and --retry. It's still not neat enough and there are things to add as saem has suggested, however I think improving compiler tooling is pretty important. In essence:
|
71fca8e
to
d9eb7da
Compare
This is better, I can make a bunch of other improvements in the weekend, we should be in good shape. |
fd5b686
to
6a90d6a
Compare
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.
[TESTAMENT]
-> testament:
is the only nit I have left.
Great work!
remove dirty template parser in template Comments and style as per @alaviss documentation and personal style preferences predecate styleechos with optFailing check introduce techo to help in the interim Changed techo to msg; added cache failed results extract retries lost still confsed retry implementation reduce msg proc branching
6a90d6a
to
d978bd2
Compare
bors r+ |
Build succeeded: |