Skip to content
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.

Sign up for GitHub

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

Jump to bottom

v4.PublishIT.shouldPublishQoS2Message fails only on GitHub Actions #1182

Open
jfallows opened this issue Aug 4, 2024 · 0 comments
Open

v4.PublishIT.shouldPublishQoS2Message fails only on GitHub Actions #1182

jfallows opened this issue Aug 4, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@jfallows
Copy link
Contributor

jfallows commented Aug 4, 2024 

[INFO] Running io.aklivity.zilla.runtime.binding.mqtt.internal.stream.server.v4.PublishIT
Error:  Tests run: 10, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 4.435 s <<< FAILURE! - in io.aklivity.zilla.runtime.binding.mqtt.internal.stream.server.v4.PublishIT
Error:  io.aklivity.zilla.runtime.binding.mqtt.internal.stream.server.v4.PublishIT.shouldPublishQoS2Message  Time elapsed: 0.152 s  <<< FAILURE!
org.junit.ComparisonFailure: 
Specified behavior did not match expected:<...ead "message"

read [zilla:data.ext ${mqtt:matchDataEx()
                            .typeId(zilla:id("mqtt"))
                            .publish()
                                .qos("EXACTLY_ONCE")
                                .build()
                            .build()}
read "message3"]
> but was:<...ead "message"

read [aborted]
>

[INFO] Running io.aklivity.zilla.runtime.binding.mqtt.internal.stream.server.v4.PingIT
Warning:  Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.003 s - in io.aklivity.zilla.runtime.binding.mqtt.internal.stream.server.v4.PingIT

zilla-build-21-1181.zip
@jfallows jfallows added the bug Something isn't working label Aug 4, 2024
jfallows added a commit that referenced this issue Aug 4, 2024
@jfallows
Ignore IT that fails intermittently on GitHub Actions, see #1182
22b889d
jfallows added a commit that referenced this issue Aug 5, 2024
@jfallows
Update MQTT wildcard processing for client topic patterns (#1179)
b660d48 
* Update MQTT wildcard processing for client topic patterns

* Ignore IT that fails intermittently on GitHub Actions, see #1182

* Update code coverage metrics

* Update MQTT wildcard processing for client topic patterns
@jfallows jfallows added the needs_triage Unknowns need to be addressed label Aug 27, 2024
@vordimous vordimous removed the needs_triage Unknowns need to be addressed label Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jfallows @vordimous