View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0031547 | Runner | Windows (YYC) | Public | 2019-12-20 14:02 | 2020-01-13 16:23 |
Reporter | Dan | Assigned To | Russell Kay | ||
Priority | Medium | Severity | C - General | Reproducibility | 100% |
Status | Resolved | Resolution | Fixed | ||
Platform | Windows YYC | OS | Windows 10 | OS Version | 1909 |
Product Version | 2.2.5 | ||||
Target Version | 2.3.0 | Fixed in Version | 2.3.0 | ||
Summary | 0031547: Windows YYC: Comparing irandom() whole to a decimal number ignores the fractional part and returns true | ||||
Description | As the attached sample shows, in Windows YYC comparing to an irandom() value appears to floor both sides, so all floating point values return true as long as the integer part would be a match. VM does not do this, so there is an inconsistency there also. Expected: The test only returns 1 "match" - when time is equal to exactly 3.0. (This is what VM does) | ||||
Steps To Reproduce | 1. Run the attached sample for Windows YYC. 2. Observe the counter increments in 0.01 steps. 3. Observe that when it reaches 3.0 it starts returning true until time reaches 4.0, and so ends up with 100 matches. Repro: 100% | ||||
Tags | No tags attached. | ||||
1.4 Found In | |||||
2.x Runtime Found In | 2.2.5.378 | ||||
2.x Runtime Verified In | |||||