Skip to content

RANGER-5602: Local build failure due to unit test failure in TestPolicyACLs #948

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

Open
ChinmayHegde24 wants to merge 1 commit into
base: master
Choose a base branch
from
+1 −1
Open

RANGER-5602: Local build failure due to unit test failure in TestPolicyACLs #948

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion agents-common/src/test/java/org/apache/ranger/plugin/policyengine/TestPolicyACLs.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -119,7 +119,7 @@ private void runTests(InputStreamReader reader, String testName) {
RangerPluginContext pluginContext = new RangerPluginContext(new RangerPluginConfig(serviceType, null, "test-policy-acls", "cl1", "on-prem", policyEngineOptions));
RangerPolicyEngine policyEngine = new RangerPolicyEngineImpl(testCase.servicePolicies, pluginContext, null);

testCase.tests.parallelStream().filter(Objects::nonNull).forEach(oneTest -> {
testCase.tests.stream().filter(Objects::nonNull).forEach(oneTest -> {
Copy link
Copy Markdown
Contributor

@vyommani vyommani May 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please don't change it from parallelStream to stream. I’ve been investigating this and the parallel execution was an intentional change made as part of RANGER-5115.

We need more analysis to determine the correct fix for this test failure. The test only started failing a couple of hours ago in my local env, so I haven’t finished the root cause analysis yet.

If this is blocking, we can temporarily disable the test, but I recommend not modifying the test logic.

@ChinmayHegde24 If it’s urgent, please disable the test for now. We’ll analyze the failure and push a proper fix

Copy link
Copy Markdown
Contributor Author

@ChinmayHegde24 ChinmayHegde24 May 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vyommani Sure , that will cause only issues in local build, in CI it's fine anyway so it'll not block there

RangerAccessRequestImpl request = new RangerAccessRequestImpl(oneTest.resource, RangerPolicyEngine.ANY_ACCESS, null, null, null);

request.setResourceMatchingScope(oneTest.resourceMatchingScope);
Expand Down
Loading