Running ide/projectui tests in the CI checks - #9603
Conversation
|
I squash my commits and integrate. |
projectui tests are missing from CI checkside/projectui tests are missing from CI checks
ide/projectui tests are missing from CI checkside/projectui tests in the CI checks
de131b2 to
288b53d
Compare
|
please use CI resources responsibly. We don't have to run all jobs in PRs which modify tests of a single module. Unless those are base files or there are other risks of side effects . The ide job is always active so this should run if I see this correctly. Also when activating a new set of tests, I would recommend to run them in a loop a little bit to check if they are reliable in case this hasn't been done yet. We continue to have stability issues in CI - tracking them down is time consuming (#8183). |
For a while I wasn't sure what this comment is about, but now I know...
OK. That's fair. We don't need to run other tests if the changes are only in |
With 68a9f6d I executed: e.g. 37 successful subsequent runs. I guess that's good enough to enter the CI, right @mbien? |
68a9f6d to
fdd17ea
Compare
Thanks. Squashed and will commit once the CI is green again. |
sounds good to me, thanks for checking before integration |
projectuitests in the CIorg.netbeans.modules.project.ui.ProjectsRootNodeTest- fixed in 64b8585org.netbeans.modules.project.ui.ProjectsRootNodeInitializedSoonerTest- removed