Re: Jenkins build became unstable: epics-base-3.14-win64 #105

[Andrew Johnson <anj@aps.anl.gov>]

On 02/23/2016 05:46 PM, APS Jenkins wrote:
> See <https://jenkins.aps.anl.gov/job/epics-base-3.14-win64/105/changes>

I guess I should have run these on Windows before merging:

> ok 592 - -1431655766.1 OR 0
> not ok 593 - 2863311530.1 OR 0
> # Expected result is 0xaaaaaaaa (2863311530), actually got 0x80000000 (2147483648)
>         Double 2.86331e+009
>         Integer 0 (0x0)
>         BIT_OR
> ok 594 - 0 OR -1431655766.1
> ok 595 - 0 OR 2863311530.1

That's interesting, #593 failed but #595 passed; exactly the same
operation but with swapped inputs. The code is this:

        case BIT_OR:
            utop = *ptop--;
            *ptop = (epicsInt32) ((epicsUInt32) *ptop | utop);
            break;


> ok 596 - -1431655766.1 XOR 0
> not ok 597 - 2863311530.1 XOR 0
> # Expected result is 0xaaaaaaaa (2863311530), actually got 0x80000000 (2147483648)
>         Double 2.86331e+009
>         Integer 0 (0x0)
>         BIT_EXCL_OR
> ok 598 - 0 XOR -1431655766.1
> ok 599 - 0 XOR 2863311530.1

Definitely a pattern there...

> ok 600 - -1431655766.1 AND 0xffffffff
> not ok 601 - 2863311530.1 AND 0xffffffff
> # Expected result is 0xaaaaaaaa (2863311530), actually got 0x80000000 (2147483648)
>         Double 2.86331e+009
>         Integer -1 (0xffffffff)
>         BIT_AND
> ok 602 - 0xffffffff AND -1431655766.1
> ok 603 - 0xffffffff AND 2863311530.1
> ok 604 - ~ -1431655766.1
> not ok 605 - ~ 2863311530.1
> # Expected result is 0x55555555 (1431655765), actually got 0x7fffffff (2147483647)
>         Double 2.86331e+009
>         BIT_NOT
> ok 606 - -1431655766.1 >> 0
> not ok 607 - 2863311530.1 >> 0
> # Expected result is 0xaaaaaaaa (2863311530), actually got 0x80000000 (2147483648)
>         Double 2.86331e+009
>         Integer 0 (0x0)
>         RIGHT_SHIFT
> ok 608 - -1431655766.1 >> 0.1
> not ok 609 - 2863311530.1 >> 0.1
> # Expected result is 0xaaaaaaaa (2863311530), actually got 0x80000000 (2147483648)
>         Double 2.86331e+009
>         Double 0.1
>         RIGHT_SHIFT
> ok 610 - -1431655766.1 << 0
> not ok 611 - 2863311530.1 << 0
> # Expected result is 0xaaaaaaaa (2863311530), actually got 0x80000000 (2147483648)
>         Double 2.86331e+009
>         Integer 0 (0x0)
>         LEFT_SHIFT
> ok 612 - -1431655766.1 << 0.1
> not ok 613 - 2863311530.1 << 0.1
> # Expected result is 0xaaaaaaaa (2863311530), actually got 0x80000000 (2147483648)
>         Double 2.86331e+009
>         Double 0.1
>         LEFT_SHIFT

Anybody got any ideas? Tomorrow...

- Andrew

-- 
There are only two hard problems in distributed systems:
  2. Exactly-once delivery
  1. Guaranteed order of messages
  2. Exactly-once delivery
 -- Mathias Verraes