[MTCGA]: new failures in builds [5882651] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *New test failure in master-nightly IoStatisticsSelfTest.testPersistentIOGlobalStat https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=819520953627395091&branch=%3Cdefault%3E&tab=testDetails Changes may lead to failure were done by - aleksey plekhanov https://ci.ignite.apache.org/viewModification.html?modId=917288 - atri sharma https://ci.ignite.apache.org/viewModification.html?modId=917319 - mikhail petrov https://ci.ignite.apache.org/viewModification.html?modId=917314 - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 14:21:56 20-02-2021
Apache Ignite 3.x: order in repository
Hi, Igniters! When we started Ignite 3.x in new repository, not only we have received a chance to cleanup codebase, but to maintain some order in development tools, like GitHub. Currently in 2.x repository we have lots of stalled PRs and branches, which not only clog the repository, but also indirectly influence TC performance (due to necessity to check for updates every ref: branches and PRs). Could I suggest we devise some recommendations for using PR's and branches in new repo and add some rules about stalled PRs at least, like closing them if inactive for some time. Also we can activate some settings in repo's configuration, like auto delete branch after PR is merged. WDYT?
[jira] [Created] (IGNITE-14216) control.sh --cache list . --seq: NullPointerException
Surkov Aleksandr created IGNITE-14216: - Summary: control.sh --cache list . --seq: NullPointerException Key: IGNITE-14216 URL: https://issues.apache.org/jira/browse/IGNITE-14216 Project: Ignite Issue Type: Bug Components: control.sh Affects Versions: 2.9.1 Reporter: Surkov Aleksandr Attachments: full-stack-trace.txt Executing the following command throws an error: _control.sh --cache list . --seq_ -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Apache Ignite 3.x: order in repository
+1 - Close inactive PRs (1 month or so?) - Enable main branch protection (no force pushes, require linear history, require status checks) On Sat, Feb 20, 2021 at 2:31 PM Petr Ivanov wrote: > Hi, Igniters! > > > When we started Ignite 3.x in new repository, not only we have received a > chance to cleanup codebase, but to maintain some order in development > tools, like GitHub. > Currently in 2.x repository we have lots of stalled PRs and branches, > which not only clog the repository, but also indirectly influence TC > performance (due to necessity to check for updates every ref: branches and > PRs). > > Could I suggest we devise some recommendations for using PR's and branches > in new repo and add some rules about stalled PRs at least, like closing > them if inactive for some time. > Also we can activate some settings in repo's configuration, like auto > delete branch after PR is merged. > > > WDYT?
