An AP unittest failure was not caught and reported when it first occurred. Now that the unittest failures are correctly being caught, the packages with such failures are now being tracked down and repaired.
Thies failure is one of them.
Regarding this failure, Perry said:
"... the one in AP might have been caused by a change Jim and I made 2 mos. ago. Has it been a long time since the tests on ap was examined? I don't think anything that I did recently could have caused this.
I am going to suggest that we disable this assert, since the test runs fine without the one assert on lines 238-239 of $AP_DIR/tests/sourceClusterTable.cc. I just commented out this assert, and the test is otherwise OK. "