[
https://issues.apache.org/jira/browse/IGNITE-11356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774873#comment-16774873
]
Ignite TC Bot commented on IGNITE-11356:
----------------------------------------
{panel:title=--> Run :: All (Nightly): Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Disk Page Compressions{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3144521]]
* IgnitePdsExchangeDuringCheckpointTest.testExchangeOnNodeJoin (last started)
{panel}
[TeamCity *--> Run :: All (Nightly)*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3142214&buildTypeId=IgniteTests24Java8_RunAllNightly]
> Test framework: Remove custom assumption exceptions handling
> ------------------------------------------------------------
>
> Key: IGNITE-11356
> URL: https://issues.apache.org/jira/browse/IGNITE-11356
> Project: Ignite
> Issue Type: Task
> Reporter: Ivan Pavlukhin
> Assignee: Ivan Pavlukhin
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It turns out that custom handling of {{AssumptionViolatedException}} can be
> removed. Currently with custom handling tests with unmet assumptions are
> marked as passed. With default handling failed assumptions on instance level
> mark tests as ignored.
> Note: on class level reporting in case of unmet assumptions does not look
> perfect. But with custom handling a particular test is not included into TC
> report at all.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
