- Notifications
You must be signed in to change notification settings - Fork118
Expose wf schedule/execution time#333
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
…on time in test framework
meiliang86 commentedJul 2, 2019
| longgetExecutionTimeMillis() { | ||
| returnTimeUnit.NANOSECONDS.toMillis( | ||
| decisionTask.getHistory().getEvents().get(1).getTimestamp()); |
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 it is always true. For example signalWithStart will have signal as a second event.
Also when cron workflow is waiting for exectution all received signals will be put before DecisionTaskScheduled.
CLAassistant commentedApr 7, 2022
Liang Mei seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, pleaseadd the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let usrecheck it. |
Also fix cron first execution time in test framework