ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Ozerov <voze...@gridgain.com>
Subject Cache test failures status.
Date Mon, 09 Feb 2015 13:51:42 GMT

I filed a bunch of tickets for broken cache tests. Here is brief summary:

*IGNITE-203* - IgniteCache.randomEntry() is not implemented what causes
test failures.
*IGNITE-205 *- JDBC store tests are broken, possibly due to incorrect
placement of particular XML file.
*IGNITE-206 *- several tests are borken because IgniteCache.loadAll() with
replaceExistingValues=true semantics is different from old
*IGNITE-207 *- removal of unexsting entry in OPTIMISTIC transaction returns
"true" violating Cache.remove() contract.
*IGNITE-208 *- NEAR_ONLY node transaction can be committed even if DHT
transaction was rolled back,
*IGNITE-209 *- expiration is not propagated to NEAR_ONLY cache entry.

Vladimir Ozerov: IGNITE-203;
Andrey Novikov: IGNITE-205;
Semen Boikov: IGNITE-206;
Alexy Goncharuk: IGNITE-207, IGNITE-208, IGNITE-209.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message