On Monday, July 6, 2015 at 5:01:39 PM UTC-4, jean-pierre.muench wrote: > > Sorry, found this just after hitting the "send" button: > > Could you please download the current GitHub master branch, select > Win32|Release, right-click on "cryptest" and hit "build"? (-> no batch > build) > > I also just tried the batch build and also failed in the same way... > Yep, it sounds like you were doing what I was doing - build all the variants of Cryptlib (4x) and Cryptest (4x), but not the others (another 12x or so).
> I've also found the exact same errors you've found - even with 5.6.2 . > So it's probably not something we have introduced, although we have to > fix it now. > Yes, agreed. So there are two problems here. First is the immediate break/fix, which includes the UserThreadTimer I broke. We will get to that in turn. If anyone feels overwhelmed, I can back-out that check-in. The second is a bigger problem and it is, why has issue has manifested so long undetected? I'm more interested in the second problem because that indicates problems in our processes. We need solid processes in place to help us avoids these breaks in the first place. As a matter of philosophy, breaks/fixes don't bother me. You can't make an omelet without breaking eggs... Shit happens... Etc... But I do expect them to be detected and fixed in a timely manner. Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
