-
Notifications
You must be signed in to change notification settings - Fork 7
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
Fix: unwrap event & fix groups
typo.
#14
Conversation
f399d65
to
5715371
Compare
@@ -20,9 +20,9 @@ pub enum EventType { | |||
#[serde(rename = "message_event")] | |||
Message { message: String }, | |||
#[serde(rename = "success_event")] | |||
Success { groups: String }, | |||
Success { group: String }, |
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.
Mind adding a changelog entry? https://github.com/testground/sdk-rust/blob/master/CHANGELOG.md Also is there any way to make the CI fail on this error, to prevent regressions in the future? sdk-rust/.github/workflows/ci.yml Lines 106 to 114 in 5c50ba4
|
9819c27
to
2c02b88
Compare
(changelog updated and follow-up issue created in pl-strflt/ipdx#20) |
Mhhh, with current
with this branch I get:
Testground version:
Still need to debug this further. |
Could you run the test a couple of times and share the full log when this branch fails? (I couldn't reproduce),
That's the dashboard result we should care about: |
@mxinden fwiw running on the CI (with the other patch that captures failures correctly): master fails consistently: this branch passes: |
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.
Not able to reproduce the failures I have been seeing. Sorry for the noise.
Tested once again locally. Both log output and dashboard report run with this branch as success.
Will merge here. Thanks @laurentsenta!
When testing with the latest testground, the example would end in "failed" state despite a successful run. When I looked at the JSON, it looked like the payload for events are malformed and they are not registered by the testground runner.
This changes the payload from:
to: