Loading...

repo-discuss@googlegroups.com

[Prev] Thread [Next]  |  [Prev] Date [Next]

Re: NoBlock + Prolog Chris Harris Thu Feb 16 13:01:47 2012

We are running patch version based on 2.2.2-rc1. I can confirm it contains
c4a1e135ce32ee2d29dd756873ab23b64722271d.

So two rules should look like this ? :

legacy_submit_rule('NoBlock', Label, Id, Min, Max, T) :- !, T = ok(_), true.
legacy_submit_rule('NoOp', Label, Id, Min, Max, T) :- !, T = ok(_), true.

Thanks,

Chris

On Thu, Feb 16, 2012 at 2:32 PM, Martin Fick <[EMAIL PROTECTED]> wrote:

> On Thursday, February 16, 2012 12:22:00 pm Chris Harris
>> wrote:
>> > I am running into a problem with using the "NoBlock"
>> > CategoryFunction. Basically its preventing changes from
>> > being submitted.  I see there was a patch to the prolog
>> > recently, which made it into 2.2.2-rc1. When I trap the
>> > results of running the prolog rule in the debugger I see
>> > the following, there seem to be two terms in the array
>> > (after line ChangeControl.java:285):
>> >
>> > [ok(submit(label(Verified,ok(user(1000000))),label(Code-
>> > Review,ok(user(1000000))),label(Build-Status,ok(_53168A4C
>> > )))),
>> > not_ready(submit(label(Verified,ok(user(1000000))),label
>> > (Code- Review,ok(user(1000000))),label(Build-
>> > Status,impossible(unsupported(NoBlock)))))]
>> >
>> > So it looks like the end rule is being reached. The
>> > second term seems to be causing the problem. Can anyone
>> > familiar with this code give me some pointers?
>>
>>
>> What version are you running?
>>
>> -Martin
>>
>> --
>> Employee of Qualcomm Innovation Center, Inc. which is a
>> member of Code Aurora Forum
>>
>
>

-- 
To unsubscribe, email [EMAIL PROTECTED]
More info at http://groups.google.com/group/repo-discuss?hl=en