I wonder if these instances are maybe related to unexpected time changes on the machine? Maybe the test can be adjusted to at least print out the expected and what it thinks is the current time. Myrna
- Failure in testCurrentTimestamp on 10.5 codeline using ... Mamta Satoor
- Re: Failure in testCurrentTimestamp on 10.5 codeli... Knut Anders Hatlen
- Re: Failure in testCurrentTimestamp on 10.5 co... Knut Anders Hatlen
- Re: Failure in testCurrentTimestamp on 10.5 co... Myrna van Lunteren
