Hello, Maxim.
+1 from me for migrating to checkstyle.
Oleg, there is plugin for IDEA with 2mln downloads -
https://plugins.jetbrains.com/plugin/1065-checkstyle-idea
I propose do the following:
1. Migrate current checks to checkstyle.
2. Apply checks to all Ignite modules. Currently, only core m
Igniters,
When I was working with flaky tests, I was surprised that one of the
reasons for failure was a log appender blocking the console.
I suppose it happened because of a TeamCity agent communicating with java
out through Linux pipe. This is a problem for tests with 1GB log history.
Our t
Is build configuration Inspections [Core] meant to transform into single
all-modules check build configuration (without module subdivision)?
> On 11 Feb 2019, at 11:02, Nikolay Izhikov wrote:
>
> Hello, Maxim.
>
> +1 from me for migrating to checkstyle.
>
> Oleg, there is plugin for IDEA wit
Vasiliy Sisko created IGNITE-11284:
--
Summary: Web console: Actualize grid configuration: query entity
and Pojo store
Key: IGNITE-11284
URL: https://issues.apache.org/jira/browse/IGNITE-11284
Project:
Vlad,
Your case is valid as well. And DebugSuite will not help there. But I
talk about another case. And I have already reproduced several tests
after repetitive execution of a single test on TC. So, my case also
seems valid.
пн, 11 февр. 2019 г. в 10:43, Vladislav Pyatkov :
>
> Hi,
>
> I think m
Hello, Petr.
Are you saying that we have not single build task? And each module builds
when it required? If yes, then I propose to create a task like "Licence
check" which will be run for every patch.
My point is that violation of codestyle should be treated as hard as
compile error.
пн, 11 февр
I was asking about how many build configuration is intended? One for all and
multiple per module?
With IDEA inspections it was going to be build configuration per module.
> On 11 Feb 2019, at 11:24, Nikolay Izhikov wrote:
>
> Hello, Petr.
>
> Are you saying that we have not single build ta
Petr, we should have 1 configuration for project, may be 1 configuration
per programming language.
пн, 11 февр. 2019 г., 11:33 Petr Ivanov mr.wei...@gmail.com:
> I was asking about how many build configuration is intended? One for all
> and multiple per module?
>
> With IDEA inspections it was go
Alexey Kuznetsov created IGNITE-11285:
-
Summary: Conflicting javadocs for PagesFillFactor
Key: IGNITE-11285
URL: https://issues.apache.org/jira/browse/IGNITE-11285
Project: Ignite
Issue T
++1 from my side. It is very interesting how overall RunAll run time will
be decreased.
My previous experience with TeamCity shows that removing pressure from the
console and using adequate logging instead may bring x1.5 - x2 performance
boost for tests.
One more benefit of moving from synced str
Andrey Kuznetsov created IGNITE-11286:
-
Summary: Add console prompt for password in control.(sh|bat) script
Key: IGNITE-11286
URL: https://issues.apache.org/jira/browse/IGNITE-11286
Project: Ignite
Hello!
Can we do IGNITE_QUIET=true for runAlls triggered by bot (along with
SCALE_FACTOR) and false for manually triggered builds (or retriggered
failures)?
Regards,
--
Ilya Kasnacheev
пн, 11 февр. 2019 г. в 13:03, Dmitriy Pavlov :
> ++1 from my side. It is very interesting how overall RunAll
Alexander Lapin created IGNITE-11287:
Summary: JDBC Thin: best effort affinity
Key: IGNITE-11287
URL: https://issues.apache.org/jira/browse/IGNITE-11287
Project: Ignite
Issue Type: Task
Maksim,
Generally I like the idea. But there is one thing which bothers me a
little bit. Usually I use "Download full build log" link to download
log and then examine it as a single file. AFAIK artifact with logs
contains several files. Could you suggest a way how can I conveniently
explore files
Pavel Voronkin created IGNITE-11288:
---
Summary: Missing SO_LINGER in TcpDiscovery and TcpCommunicationSpi
causing SSLSocket.close() deadlock.
Key: IGNITE-11288
URL: https://issues.apache.org/jira/browse/IGNITE-11
Ivan Pavlukhin created IGNITE-11289:
---
Summary: BPlusTree.AbstractForwardCursor can use obsolete page
Key: IGNITE-11289
URL: https://issues.apache.org/jira/browse/IGNITE-11289
Project: Ignite
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
Ivan,
Yes. It happens because we use the RollingFileAppender for a file logging.
This appender has the next properties:
Can I increase MaxFileSize by 200MB or more? I suppose these limits were
added for cases when the test writes a log. It makes the guarantee that
logs less than 10*10 = 100MBs
Sergey Chugunov created IGNITE-11290:
Summary: History of server node IDs should be passed to new nodes
with NodeAddedMessage
Key: IGNITE-11290
URL: https://issues.apache.org/jira/browse/IGNITE-11290
Maksim,
sounds good.
1) Can we just turn off log rollover?
2) I believe, that we need the ability to override this by setting
parameter for Run All.
On Mon, Feb 11, 2019 at 4:12 PM Maksim Stepachev
wrote:
> Ivan,
>
> Yes. It happens because we use the RollingFileAppender for a file logging.
Vladislav Pyatkov created IGNITE-11291:
--
Summary: Assertion error in time of rebalance completion lead to
to critical failure node
Key: IGNITE-11291
URL: https://issues.apache.org/jira/browse/IGNITE-11291
Dmitry Sherstobitov created IGNITE-11292:
Summary: There is no way to disable WAL for cache in group
Key: IGNITE-11292
URL: https://issues.apache.org/jira/browse/IGNITE-11292
Project: Ignite
Ivan Bessonov created IGNITE-11293:
--
Summary: NPE in TcpCommunicationSpi
Key: IGNITE-11293
URL: https://issues.apache.org/jira/browse/IGNITE-11293
Project: Ignite
Issue Type: Bug
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
24 matches
Mail list logo
