You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2013/09/28 07:49:30 UTC

Jenkins build became unstable: Knox-master-verify #439

See <https://builds.apache.org/job/Knox-master-verify/439/changes>


Re: Jenkins build became unstable: Knox-master-verify #439

Posted by Dilli Arumugam <da...@hortonworks.com>.
Kevin,

Sorry that the fix for Knox-163 broke the tests in
IdentityAssertionHttpServletRe**questWrapperTest.

Have modified the tests in IdentityAssertionHttpServletRe**questWrapperTest
in the light of changes done for Knox-163.

Ran
mvn -Prelease clean install
Got a clean build and pushed the changes.

Apache Jira seems to be down now.
So, could not add/update Jira or attach patches there.

Thanks
Dilli


On Sat, Sep 28, 2013 at 9:49 AM, Kevin Minder
<ke...@hortonworks.com>wrote:

> And another thing, it is best to monitor
> https://builds.apache.org/job/**Knox-master-verify/<https://builds.apache.org/job/Knox-master-verify/>
> after a push until you see a clean biuld.
>
>
> On 9/28/13 1:49 AM, Apache Jenkins Server wrote:
>
>> See <https://builds.apache.org/**job/Knox-master-verify/439/**changes<https://builds.apache.org/job/Knox-master-verify/439/changes>
>> >
>>
>>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity
> to which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: Jenkins build became unstable: Knox-master-verify #439

Posted by Kevin Minder <ke...@hortonworks.com>.
And another thing, it is best to monitor
https://builds.apache.org/job/Knox-master-verify/
after a push until you see a clean biuld.

On 9/28/13 1:49 AM, Apache Jenkins Server wrote:
> See <https://builds.apache.org/job/Knox-master-verify/439/changes>
>


-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Jenkins build is back to stable : Knox-master-verify #440

Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Knox-master-verify/440/changes>


Re: Jenkins build became unstable: Knox-master-verify #439

Posted by Kevin Minder <ke...@hortonworks.com>.
Dilli,

You recent changes broke the build.  Probably KNOX-163.  There are some 
assumptions in IdentityAssertionHttpServletRequestWrapperTest that are 
no longer true after your change.  So two things:

1) Everyone MUST always run "ant verify" or its equivalent "mvn 
-Prelease clean install" before pushing any changes.  This is the same 
command that Jenkins runs.

2) You need to carefully consider the assumptions made by 
IdentityAssertionHttpServletRequestWrapperTest to determine if they are 
invalid or if your changes are invalid.

Keivn.

On 9/28/13 1:49 AM, Apache Jenkins Server wrote:
> See <https://builds.apache.org/job/Knox-master-verify/439/changes>
>


-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.