Hi Yuan,
I see that we keep on adding options to enable/disable some parts of the
testsuite.
However, should we think about converting most of these tests into unit-tests
and not always run them against a full running cluster.
I doubt that a full system is indeed needed in most cases.
Unit-Tests are much more lightweight and can run a lot quicker and in parallel.
Chris
Von: Yuan Tian <jackietie...@gmail.com>
Datum: Freitag, 16. August 2024 um 09:12
An: dev <dev@iotdb.apache.org>
Betreff: Seperate Table Model related ITs from Old Tree Model ITs
Hi all,
Since Table Model codes have been merged into master branch, and we keep
adding more ITs for Table Model which will end up being more than tree
model. And The development of the table model is in a rapid iteration
cycle, so there are many pull requests (PRs) being made to the master
branch every day. As the table model's IT increases, the time for
Continuous Integration (CI) is getting longer, and the waiting time for CI
is always frustrating.
In this PR[1], I have distinguished the IT of the table model and the tree
model using different annotations. The IT class of the tree model still
uses the original @Category({LocalStandaloneIT.class, ClusterIT.class}).
The IT class of the table model uses the newly added
@Category({TableLocalStandaloneIT.class,
TableClusterIT.class}).
I have also added two GitHub actions to run the table model's IT in
parallel.
If anyone wants to manually run the table model's IT under the 1c1d
environment, you can use the following Maven command:
mvn clean verify -DskipUTs -pl integration-test -am -PTableSimpleIT -P
with-integration-tests
If anyone wants to manually run the table model's IT under the 1c3d
environment, you can use the following Maven command.
mvn clean verify -DskipUTs -pl integration-test -am -PTableClusterIT -P
with-integration-tests
[1] https://github.com/apache/iotdb/pull/13196
Best regards,
-----------------------
Yuan Tian
