Hi, Petr!
Profile "check-test-suites" handles all tests in another way, it just
verifies that all tests are suited. No tests run then.
As I understand the [BUILD] job goal is preparing a .zip archive to
distribute it for other jobs. I think it is a valid place to put sanity
checks. If a check
I'm sorry, I forgot to write on dev-list about this agent.
Indeed the target files were removed manually.
> On 24 Feb 2021, at 19:32, Max Timonin wrote:
>
> Looks like somebody fixed that. An hour ago Build succeeded at last [1]. It
> was the first successful job for a long time. Thanks!
>
>
Nikolay Izhikov created IGNITE-14241:
Summary:
IgniteCacheAbstractQuerySelfTest#testClientQueryExecutedEventsIncludeSensitive
broken
Key: IGNITE-14241
URL: https://issues.apache.org/jira/browse/IGNITE-14241
Ivan Daschinskiy created IGNITE-14240:
-
Summary: Handle authentication error on python thin client properly
Key: IGNITE-14240
URL: https://issues.apache.org/jira/browse/IGNITE-14240
Project:
Hi, all!
What do you think if we add the check in the TC [Build] job. Currently
[Build] runs also check for licences, checkstyle [1]:
mvn *install* -Pall-java,all-scala,scala,*licenses*,lgpl,examples,
*checkstyle* -DskipTests -Dmaven.javadoc.skip=true %MAVEN_MODULES_STRING%.
So let's add the
Looks like somebody fixed that. An hour ago Build succeeded at last [1]. It
was the first successful job for a long time. Thanks!
removed directory '/opt/buildagent/.m2/repository/org/apache/ignite'
Process exited with code 0
[1]
Vyacheslav Koptilin created IGNITE-14239:
Summary: Raft based implementation of atomic protocol
Key: IGNITE-14239
URL: https://issues.apache.org/jira/browse/IGNITE-14239
Project: Ignite
Vyacheslav Koptilin created IGNITE-14238:
Summary: Creating and destroying caches
Key: IGNITE-14238
URL: https://issues.apache.org/jira/browse/IGNITE-14238
Project: Ignite
Issue
Vyacheslav Koptilin created IGNITE-14237:
Summary: Affinity function
Key: IGNITE-14237
URL: https://issues.apache.org/jira/browse/IGNITE-14237
Project: Ignite
Issue Type: Sub-task
Vyacheslav Koptilin created IGNITE-14236:
Summary: Provide a new version of cache API
Key: IGNITE-14236
URL: https://issues.apache.org/jira/browse/IGNITE-14236
Project: Ignite
Issue
Hi, Igniters.
Sincerely asking you to help me with testing new RPM package for apache ignite
3.x [1]
Currently what is needed to be tested — successful installation and binary run
under most of RHEL based distributions: Red Hat, CentOS, Oracle Linux, Fedora,
etc.
Any other thoughts and
Vyacheslav Koptilin created IGNITE-14235:
Summary: Provide a minimal cache/table configuration
Key: IGNITE-14235
URL: https://issues.apache.org/jira/browse/IGNITE-14235
Project: Ignite
Igniters,
Did not we agree on disabling MVCC suites? Why does TC bot still run them?
2021-02-20 8:16 GMT+03:00, Atri Sharma :
> I ran the MVCC Test Suite 7 on branch with my changes a couple of
> times with no failures.
>
> On Sat, Feb 20, 2021 at 8:37 AM wrote:
>>
>> Hi Igniters,
>>
>> I've
Vyacheslav Koptilin created IGNITE-14234:
Summary: Tracing framework
Key: IGNITE-14234
URL: https://issues.apache.org/jira/browse/IGNITE-14234
Project: Ignite
Issue Type: New Feature
Vyacheslav Koptilin created IGNITE-14233:
Summary: Metrics framework
Key: IGNITE-14233
URL: https://issues.apache.org/jira/browse/IGNITE-14233
Project: Ignite
Issue Type: New Feature
Kirill Gusakov created IGNITE-14232:
---
Summary: IgniteCliInterfaceTest and ProgressBarTest fails in some
terminals
Key: IGNITE-14232
URL: https://issues.apache.org/jira/browse/IGNITE-14232
Project:
Sergey Chugunov created IGNITE-14231:
Summary: IGNITE_ENABLE_FORCIBLE_NODE_KILL flag is not supported in
inverse connection request scenario
Key: IGNITE-14231
URL:
Anton,
Your improvement is very important, for sure, but it's almost 2 months
have passed since the initiation of the release branch. I think we
should prepare the changes as fast as possible for now and initiate
with the next one release. In general, it would be nice to have a
release plan for
Ivan Bessonov created IGNITE-14230:
--
Summary: Port DynamicConfiguration to new underlying configuration
framework.
Key: IGNITE-14230
URL: https://issues.apache.org/jira/browse/IGNITE-14230
Project:
Yury Gerzhedovich created IGNITE-14229:
--
Summary: Calcite bug. Engine can hangs
Key: IGNITE-14229
URL: https://issues.apache.org/jira/browse/IGNITE-14229
Project: Ignite
Issue Type: Bug
Dmitriy Sorokin created IGNITE-14228:
Summary: Ducktape test of rebalance for in-memory mode
Key: IGNITE-14228
URL: https://issues.apache.org/jira/browse/IGNITE-14228
Project: Ignite
.1],
sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1614163031766, loc=false, ver=2.11.0#20210224-sha1:,
isClient=false], topVer=2, msgTemplate=null,
span=o.a.i.i.processors.tracing.NoopSpan@7e02a8f5, nodeId8=02c46b75, msg=null,
type=DISCOVERY
Dmitriy Sorokin created IGNITE-14226:
Summary: Ducktape test of rebalance
Key: IGNITE-14226
URL: https://issues.apache.org/jira/browse/IGNITE-14226
Project: Ignite
Issue Type: Test
I'd guess that one of the main problem with inactive PRs is in creation of PR
for reviewing but merging it from command line (not via GitHub interface).
Also, of course, there are lots of efforts which are abandoned after first
review, or even do not have a chance to be reviewed at all.
> On
Maxim,
https://issues.apache.org/jira/browse/IGNITE-13873
Is ready for review, is it possible to wait for it?
On Wed, Feb 24, 2021 at 12:01 AM Maxim Muzafarov wrote:
> Folks,
>
>
> I'd like to cherry-pick to the release branch the following fixes:
>
> Fix security context for JDBC bulk-load
25 matches
Mail list logo
