adoroszlai commented on PR #10377: URL: https://github.com/apache/ozone/pull/10377#issuecomment-4572384878
> Does each integration category run share the same ozone home directory, and files, or each integration category has its own fresh run environment? They use fresh environment, since they are executed on separate runner instances. > how I can make the integration(hdds) have the libhadoop native library ready too? The failed split (hdds) also had Hadoop native libraries: ``` Found Hadoop native libraries. Copying to distribution... $ mkdir -p ./lib/native $ cp -rP /home/runner/work/ozone/ozone/target/native-lib/libhadoop.dylib /home/runner/work/ozone/ozone/target/native-lib/libhadoop.so /home/runner/work/ozone/ozone/target/native-lib/libhadoop_linux_x86_64.so /home/runner/work/ozone/ozone/target/native-lib/libhadoop_osx_aarch_64.dylib ./lib/native ``` > I add the profile "test-short-circuit" in last commit, and "-Ptest-short-circuit" when integration.sh is called This results in a [new split](https://github.com/ChenSammi/ozone/actions/runs/26620467488/job/78446176291), as they are [derived](https://github.com/apache/ozone/blob/bf68f20f867de2281e0bcdf251308eabe1371587/dev-support/ci/integration_suites.sh#L22-L24) from profiles named `test-...`. It tries to run all integration tests (and times out after 1.5 hours), because there are no include/exclude rules. > One workaround is move all these test classes into one package, so they will be included in only one integration run category. You can keep them in their current package by adding `<exclude>` rules for Surefire in the existing test profiles and `<include>` rule for the new, accidental profile. https://github.com/apache/ozone/blob/bf68f20f867de2281e0bcdf251308eabe1371587/pom.xml#L2783-L2804 Otherwise please rename the new profile to something like `with-hadoop-native-lib`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
