Background:

Doing a cursor comparison like this one:

    PROCEDURE PRC_T_SAMPLE_4
    IS
        l_expected   v_ref_cursor;
        l_actual     v_ref_cursor;
    BEGIN
        OPEN l_expected FOR
            SELECT * FROM SAMPLE_TABLE WHERE filter=2; --about 20 columns and 50 rows

        OPEN l_actual FOR
            SELECT * FROM SAMPLE_TABLE WHERE filter=3; --about 20 columns and 50 rows

        ut.expect (l_expected).to_equal (l_actual);
    END;

If the test fail on the teamcity report we will have something like:
##teamcity[testFailed timestamp='2018-08-03T10:11:14.221+0200' details='Actual: |r ....... ' Name='name' ]

Inside the details the xml structure of the actual cursor and the expected cursor can be found.

Issue

Teamcity is no able to detect the testFailed. So teamcity report it as green (success) when it failed, it shall be red.

Posible problem

I opened the build log of team city and the line with all XML structure was infact in diferent lines with line breaks (every 4000 characters). So i think the problem is that the output line of the Teamcity reporter was to big and teamcity was not able to parse it.

Posible fix

Trim the details string to 2500 or 3000 characters so the ##teamcity is less than 4000.