search

checkstyle / test-configs

gsoc 24 project where will store configs for diff.groovy , https://github.com/orgs/checkstyle/projects/8
GNU Lesser General Public License v2.1
2 stars 3 forks source link

Test all-in-one bundles #120

Open romani opened 1 month ago

romani commented 1 month ago

After initial implementation of new workflow is done by Github, generate report for

We need to test all bundles to make sure that report generation can be finished.

Expected problems: oom errors due to numerous violations or timeouts.

If any problem detected, we need to reduce amount of projects to let report to finish.

PR to https://github.com/checkstyle-gsoc/checkstyle/

romani commented 1 month ago

We have a lot of bundles, so triggering should be done from phone on the go, not a laptop time. It will be good metric on how convenient to use it

romani commented 1 month ago

@relentless-pursuit , please confirm that you can test all bundles in your organization.

While we waiting for merge in main repository, we can reuse your org and simply get all bundles be tested (just to make sure reports can successfully finish).

If yes, please start. I will join. We can have single PR for one Check.

romani commented 1 month ago

We should start from running all-in-one first. If it pass it means all others will pass for sure.

relentless-pursuit commented 1 month ago

@relentless-pursuit , please confirm that you can test all bundles in your organization.

While we waiting for merge in main repository, we can reuse your org and simply get all bundles be tested (just to make sure reports can successfully finish).

If yes, please start. I will join. We can have single PR for one Check.

@romani i don't mind testing but wouldn't it be great if we could test it in main repo. because, we already have a mechanism of backwards compatability, not that the merge will hinder the existing regression testing. But, if we do testing and it can be a tough task to test all 180 checks, how can we evaluate better if not done on a main repo?

romani commented 1 month ago

wouldn't it be great if we could test it in main repo.

Yes, but it would not be quicker. Moreover, it will use GitHub quotes of execution, so we will make huge queue and we will slow down all others. In your org, you have more freedom and isolation. We will test not a workflow , but ability of reports to finish, no timeouts.

But, if we do testing and it can be a tough task to test all 180 checks

Not though, just a bit long, but we can start now, and until September trigger 180 executions for all-in-one. I will help to trigger from phone, as you already did all (except for one issue ) so convenient that it takes less 1 minutes to trigger.

relentless-pursuit commented 1 month ago

Test PRs for below Checks