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
I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
Bug Category
Other
Describe the bug
The Java build fails with
> Task :test
PolicyFormatterTests > testPoliciesStrToPrettyWithConfig() FAILED
org.opentest4j.AssertionFailedError: expected: <permit (
principal,
action == Action::"update",
resource
)
when { resource.owner == principal };
> but was: <permit (
principal,
action == Action::"update",
resource
)
when { resource.owner == principal };>
at app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at app//org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
at app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:182)
at app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:177)
at app//org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1145)
at app//com.cedarpolicy.PolicyFormatterTests.testPoliciesStrToPrettyWithConfig(PolicyFormatterTests.java:64)
14613 tests completed, 1 failed
when run as part of the downstream build from CI in the cedar repository. This presumably impacts a local build, but I have not tried to reproduce. Likely related to most recent commit to the 3.4.x release branch #241 which did touch the formatter tests.
The difference is just a missing trailing new line in the actual output, so the fix is probably just to update the expected output to remove it, but we should first check that no trailing new-line is the expected output and there isn't something funny happening that might cause a new line to be lost in the JNI layer.
Expected behavior
.
Reproduction steps
.
Code Snippet
// Put your code below this line.
Log output
// Put your output below this line
Additional configuration
No response
Operating System
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered:
Before opening, please confirm:
Bug Category
Other
Describe the bug
The Java build fails with
when run as part of the downstream build from CI in the cedar repository. This presumably impacts a local build, but I have not tried to reproduce. Likely related to most recent commit to the 3.4.x release branch #241 which did touch the formatter tests.
The difference is just a missing trailing new line in the actual output, so the fix is probably just to update the expected output to remove it, but we should first check that no trailing new-line is the expected output and there isn't something funny happening that might cause a new line to be lost in the JNI layer.
Expected behavior
.
Reproduction steps
.
Code Snippet
// Put your code below this line.
Log output
Additional configuration
No response
Operating System
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: