For me I prefer we just add a profile to hbase-assembly to generate the tarball with test jars, as only developers need to this.
For ChaosMonkey, I only used it when running ITBLL against a cluster. Let me try running failsafe locally too. Thanks. Istvan Toth <st...@apache.org> 于2025年3月18日周二 01:48写道： > > In order to get a leaner binary assembly and to reduce HBase's CVE surface > we have removed the test JARs from the normal assemblies in HBase 3 . > > However, these assemblies cannot run the HBase integration tests in the > hbase-it module. > > There are several options for handling this, but the easiest ones are: > > *1. * Adding back a separate assembly similar to the existing 2.x assembly > *1.a * but not publishing it as part of releases > *1.b * and publishing it as part of releases > *2.* Adding a profile to the assembly modules that adds the test > dependencies > > Which one would be preferable ? > Would you suggest another option ? > > My personal expectation is that only developers will run the integration > tests, who will have no problems with rebuilding the assemblies with the > test profile, so I'm leaning towards option* 2.* > > Another question is Chaos Monkey. > I have never used it myself, so I don't know what is required for running > it. > Has anyone tested it with branch-3 or trunk lately ? > Does it require test jars ? > When I was testing hbase-it, IntegrationTestMonkeys failed, but I'm not > sure why. > > Istvan
