-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
Test all-in-one bundles #120
Comments
We have a lot of bundles, so triggering should be done from phone on the go, not a laptop time. |
@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 should start from running all-in-one first. |
@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? |
Yes, but it would not be quicker.
Not though, just a bit long, but we can start now, and until September trigger 180 executions for all-in-one. |
Test PRs for below Checks
|
is this required? |
Yes, as I already noticed RegexpHeader is not working and few others |
Testing is finished at checkstyle-gsoc/checkstyle#30 (comment) All failed config will be handled at #141 |
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 checkstyle-gsoc/checkstyle#28
The text was updated successfully, but these errors were encountered: