Re: null-assign.tst failing in 'make check'

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: null-assign.tst failing in 'make check'

Rik-4
On 09/01/2016 03:38 AM, [hidden email] wrote:
Subject:
make check fails w/ recent hg
From:
"Dmitri A. Sergatskov" [hidden email]
Date:
09/01/2016 01:47 AM
To:
Octave maintainers mailing list [hidden email]
List-Post:
[hidden email]
Precedence:
list
MIME-Version:
1.0
Message-ID:
[hidden email]
Content-Type:
multipart/alternative; boundary=001a1142b98ed021e4053b6e445e
Message:
5

changeset:   22415:a338dbafcc09

>> test null-assign.tst
***** test
 a = ones (3); b = []; fail ("subsasgn (a, substruct ('()', {':',1:2}), b)", ".");
!!!!! test failed
expected error <.> but got none

This is probably due to this changeset

changeset:   22390:6cbbd550aa91
user:        John W. Eaton [hidden email]
date:        Thu Aug 25 18:18:20 2016 -0400
summary:     allow subsasgn (x, idx, zeros(0,0)) to remove elements (bug #48867)

Either the test suite in null-assign.tst needs to be updated for the new behavior, or it has caught some sort of regression.

--Rik
Reply | Threaded
Open this post in threaded view
|

Re: null-assign.tst failing in 'make check'

John W. Eaton
Administrator
Yeah, the test needs to be updated.  I'll fix it.

jwe


On 09/01/2016 12:13 PM, Rik wrote:

> On 09/01/2016 03:38 AM, [hidden email] wrote:
>> Subject:
>> make check fails w/ recent hg
>> From:
>> "Dmitri A. Sergatskov" <[hidden email]>
>> Date:
>> 09/01/2016 01:47 AM
>>
>> To:
>> Octave maintainers mailing list <[hidden email]>
>>
>> List-Post:
>> <mailto:[hidden email]>
>> Precedence:
>> list
>> MIME-Version:
>> 1.0
>> Message-ID:
>> <[hidden email]>
>> Content-Type:
>> multipart/alternative; boundary=001a1142b98ed021e4053b6e445e
>> Message:
>> 5
>>
>>
>> changeset:   22415:a338dbafcc09
>>
>> >> test null-assign.tst
>> ***** test
>>  a = ones (3); b = []; fail ("subsasgn (a, substruct ('()',
>> {':',1:2}), b)", ".");
>> !!!!! test failed
>> expected error <.> but got none
>
> This is probably due to this changeset
>
> changeset:   22390:6cbbd550aa91
> user:        John W. Eaton <[hidden email]>
> date:        Thu Aug 25 18:18:20 2016 -0400
> summary:     allow subsasgn (x, idx, zeros(0,0)) to remove elements (bug
> #48867)
>
> Either the test suite in null-assign.tst needs to be updated for the new
> behavior, or it has caught some sort of regression.
>
> --Rik