You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vadim Pakhnushev (Jira)" <ji...@apache.org> on 2022/11/28 12:39:00 UTC
[jira] [Resolved] (IGNITE-17609) Fix logs interpretation
[ https://issues.apache.org/jira/browse/IGNITE-17609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vadim Pakhnushev resolved IGNITE-17609.
---------------------------------------
Release Note: Fixed in IDEA build 231.2171, which means it should be included in the release 2023.1
Resolution: Fixed
> Fix logs interpretation
> ------------------------
>
> Key: IGNITE-17609
> URL: https://issues.apache.org/jira/browse/IGNITE-17609
> Project: Ignite
> Issue Type: Bug
> Components: build, ignite-3
> Reporter: Mikhail Pochatkin
> Assignee: Vadim Pakhnushev
> Priority: Major
> Labels: ignite-3
>
> Currently `ignite-network-annotation-processor` produce a lot of NOTE logs
> `org.apache.ignite.internal.network.processor.serialization.MessageSerializerGenerator#generateSerializer`
> In the progress of build via gradle IDEA marks these logs as errors and as result we see that build SUCCESS but has 300+ errors.
> This is not a problem of successful builds, this is a problem of developer convenience and log clarity.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)