Jenkins build is back to normal : ovirt_master_system-tests #680

[jenkins]

See 

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Jenkins build became unstable: ovirt_4.0_he-system-tests #411

[jenkins]

See 

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Jenkins build is back to stable : ovirt_4.0_he-system-tests #412

[jenkins]

See 

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Can not rebase or push updates to patches with different author

[Anton Marchukov]

Hello Shlomi.

I also had to add it to:

ovirt-engine-sdk
ovirt-engine-sdk-java
ovirt-engine-sdk-js
ovirt-engine-sdk-tests

May it be that defaults are not sane enough for this particular rule?


On Wed, Oct 19, 2016 at 11:50 PM, Shlomo Ben David 
wrote:

> Hi,
>
> This permission was set for project owners only,
> But in this specific case I think that it's the right solution, because
> these projects have customized permissions.
>
> Thanks a lot Anton.
>
> BR,
>
> Shlomi Ben-David
>
> בתאריך 19 באוק׳ 2016 15:34,‏ "Tal Nisan"  כתב:
>
> Makes perfect sense for maintainers as we have to rebase or sometimes post
>> minor updates (e.g. commit message) for patches that we are not the authors
>> of.
>> As for non maintainer users it is of small to no benefit at all so I
>> think it's the best course of action.
>>
>> Thanks.
>>
>>
>> On Wed, Oct 19, 2016 at 3:31 PM, Anton Marchukov 
>> wrote:
>>
>>> FYI. I have added Forge Author Identity to corresponding maintainers
>>> groups for master and stables branches of ovirt-engine
>>>
>>> On Wed, Oct 19, 2016 at 1:37 PM, Anton Marchukov 
>>> wrote:
>>>
 Hello Shlomi.

 May it be related to your permissions generalization work? This is
 something to consider/check.

 Anton.



 On Wed, Oct 19, 2016 at 1:26 PM, Tal Nisan  wrote:

> Hi,
>
> Up till not long ago it was possible to rebase or push updates to
> patches even if I was not the author of the patch, now I've noticed that
> when trying to do so I encounter "invalid author" error.
> For maintainers (especially in the stable branches) this is crucial
> and makes the cycle much shorter as no intervention from the original
> author is needed on trivial rebases, can you please restore the old state?
>
> Tal.
>
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


 --
 Anton Marchukov
 Senior Software Engineer - RHEV CI - Red Hat


>>>
>>>
>>> --
>>> Anton Marchukov
>>> Senior Software Engineer - RHEV CI - Red Hat
>>>
>>>
>>


-- 
Anton Marchukov
Senior Software Engineer - RHEV CI - Red Hat
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Can not rebase or push updates to patches with different author

[Sandro Bonazzola]

On Thu, Oct 20, 2016 at 3:27 PM, Anton Marchukov 
wrote:

> Hello Shlomi.
>
> I also had to add it to:
>
> ovirt-engine-sdk
> ovirt-engine-sdk-java
> ovirt-engine-sdk-js
> ovirt-engine-sdk-tests
>
> May it be that defaults are not sane enough for this particular rule?
>

I guess in some cases owner is not set.



>
>
> On Wed, Oct 19, 2016 at 11:50 PM, Shlomo Ben David 
> wrote:
>
>> Hi,
>>
>> This permission was set for project owners only,
>> But in this specific case I think that it's the right solution, because
>> these projects have customized permissions.
>>
>> Thanks a lot Anton.
>>
>> BR,
>>
>> Shlomi Ben-David
>>
>> בתאריך 19 באוק׳ 2016 15:34,‏ "Tal Nisan"  כתב:
>>
>> Makes perfect sense for maintainers as we have to rebase or sometimes
>>> post minor updates (e.g. commit message) for patches that we are not the
>>> authors of.
>>> As for non maintainer users it is of small to no benefit at all so I
>>> think it's the best course of action.
>>>
>>> Thanks.
>>>
>>>
>>> On Wed, Oct 19, 2016 at 3:31 PM, Anton Marchukov 
>>> wrote:
>>>
 FYI. I have added Forge Author Identity to corresponding maintainers
 groups for master and stables branches of ovirt-engine

 On Wed, Oct 19, 2016 at 1:37 PM, Anton Marchukov 
 wrote:

> Hello Shlomi.
>
> May it be related to your permissions generalization work? This is
> something to consider/check.
>
> Anton.
>
>
>
> On Wed, Oct 19, 2016 at 1:26 PM, Tal Nisan  wrote:
>
>> Hi,
>>
>> Up till not long ago it was possible to rebase or push updates to
>> patches even if I was not the author of the patch, now I've noticed that
>> when trying to do so I encounter "invalid author" error.
>> For maintainers (especially in the stable branches) this is crucial
>> and makes the cycle much shorter as no intervention from the original
>> author is needed on trivial rebases, can you please restore the old 
>> state?
>>
>> Tal.
>>
>>
>> ___
>> Infra mailing list
>> Infra@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>>
>
>
> --
> Anton Marchukov
> Senior Software Engineer - RHEV CI - Red Hat
>
>


 --
 Anton Marchukov
 Senior Software Engineer - RHEV CI - Red Hat


>>>
>
>
> --
> Anton Marchukov
> Senior Software Engineer - RHEV CI - Red Hat
>
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Can not rebase or push updates to patches with different author

[Shlomo Ben David]

Hi Anton,

I still didn't update other projects to the default rules.
I'll update them when I return to the office.

BR,

Shlomi Ben-David

בתאריך 20 באוק׳ 2016 04:27 PM,‏ "Anton Marchukov"  כתב:

> Hello Shlomi.
>
> I also had to add it to:
>
> ovirt-engine-sdk
> ovirt-engine-sdk-java
> ovirt-engine-sdk-js
> ovirt-engine-sdk-tests
>
> May it be that defaults are not sane enough for this particular rule?
>
>
> On Wed, Oct 19, 2016 at 11:50 PM, Shlomo Ben David 
> wrote:
>
>> Hi,
>>
>> This permission was set for project owners only,
>> But in this specific case I think that it's the right solution, because
>> these projects have customized permissions.
>>
>> Thanks a lot Anton.
>>
>> BR,
>>
>> Shlomi Ben-David
>>
>> בתאריך 19 באוק׳ 2016 15:34,‏ "Tal Nisan"  כתב:
>>
>> Makes perfect sense for maintainers as we have to rebase or sometimes
>>> post minor updates (e.g. commit message) for patches that we are not the
>>> authors of.
>>> As for non maintainer users it is of small to no benefit at all so I
>>> think it's the best course of action.
>>>
>>> Thanks.
>>>
>>>
>>> On Wed, Oct 19, 2016 at 3:31 PM, Anton Marchukov 
>>> wrote:
>>>
 FYI. I have added Forge Author Identity to corresponding maintainers
 groups for master and stables branches of ovirt-engine

 On Wed, Oct 19, 2016 at 1:37 PM, Anton Marchukov 
 wrote:

> Hello Shlomi.
>
> May it be related to your permissions generalization work? This is
> something to consider/check.
>
> Anton.
>
>
>
> On Wed, Oct 19, 2016 at 1:26 PM, Tal Nisan  wrote:
>
>> Hi,
>>
>> Up till not long ago it was possible to rebase or push updates to
>> patches even if I was not the author of the patch, now I've noticed that
>> when trying to do so I encounter "invalid author" error.
>> For maintainers (especially in the stable branches) this is crucial
>> and makes the cycle much shorter as no intervention from the original
>> author is needed on trivial rebases, can you please restore the old 
>> state?
>>
>> Tal.
>>
>>
>> ___
>> Infra mailing list
>> Infra@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>>
>
>
> --
> Anton Marchukov
> Senior Software Engineer - RHEV CI - Red Hat
>
>


 --
 Anton Marchukov
 Senior Software Engineer - RHEV CI - Red Hat


>>>
>
>
> --
> Anton Marchukov
> Senior Software Engineer - RHEV CI - Red Hat
>
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Build failed in Jenkins: ovirt_4.0_he-system-tests #414

[jenkins]

See 

Changes:

[Gal Ben Haim] Fix check-patch to collect logs on failure

--
[...truncated 1399 lines...]
##  took 2433 seconds
##  rc = 1
##
##! ERROR v
##! Last 20 log entries: 
logs/mocker-fedora-23-x86_64.fc23.he_basic_suite_4.0.sh/he_basic_suite_4.0.sh.log
##!
+ true
+ env_cleanup
+ echo '#'
#
+ local res=0
+ local uuid
+ echo ' Cleaning up'
 Cleaning up
+ [[ -e 

 ]]
+ echo '--- Cleaning with lago'
--- Cleaning with lago
+ lago --workdir 

 destroy --yes --all-prefixes
+ echo '--- Cleaning with lago done'
--- Cleaning with lago done
+ [[ 0 != \0 ]]
+ echo ' Cleanup done'
 Cleanup done
+ exit 0
Took 2258 seconds
===
##!
##! ERROR ^^
##!
##
Build step 'Execute shell' marked build as failure
Performing Post build task...
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash -xe
echo 'shell_scripts/system_tests.collect_logs.sh'

#
# Required jjb vars:
#version
#
VERSION=4.0
SUITE_TYPE=

WORKSPACE="$PWD"
OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION"
TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts"

rm -rf "$WORKSPACE/exported-artifacts"
mkdir -p "$WORKSPACE/exported-artifacts"

if [[ -d "$TESTS_LOGS" ]]; then
mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/"
fi

[ovirt_4.0_he-system-tests] $ /bin/bash -xe /tmp/hudson6452867834214450154.sh
+ echo shell_scripts/system_tests.collect_logs.sh
shell_scripts/system_tests.collect_logs.sh
+ VERSION=4.0
+ SUITE_TYPE=
+ WORKSPACE=
+ OVIRT_SUITE=4.0
+ 
TESTS_LOGS=
+ rm -rf 

+ mkdir -p 

+ [[ -d 

 ]]
+ mv 

 

 

 

 

POST BUILD TASK : SUCCESS
END OF POST BUILD TASK : 0
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash -xe
echo "shell-scripts/mock_cleanup.sh"

shopt -s nullglob


WORKSPACE="$PWD"

# Make clear this is the cleanup, helps reading the jenkins logs
cat 
+ cat
___
###
# #
#   CLEANUP   #
# #
###
+ logs=(./*log ./*/logs)
+ [[ -n ./ovirt-system-tests/logs ]]
+ tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs
./ovirt-system-tests/logs/
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/stdout_stderr.log
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/state.log
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/build.log
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/root.log
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/stdout_stderr.log
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/state.log
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/build.log
./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/root.log
./ovirt-system-tests/logs/mocker-fedora-23-

oVirt infra daily report - unstable production jobs - 113

[jenkins]

Good morning!

Attached is the HTML page with the jenkins status report. You can see it also 
here:
 - 
http://jenkins.ovirt.org/job/system_jenkins-report/113//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins


upstream_report.html
Description: Binary data
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-783) Fwd: [ovirt-users] ovirt list's smtp on blacklist?

[sbonazzo (oVirt JIRA)]

sbonazzo created OVIRT-783:
--

 Summary: Fwd: [ovirt-users] ovirt list's smtp on blacklist?
 Key: OVIRT-783
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-783
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: sbonazzo
Assignee: infra


-- Forwarded message --
From: Jiří Sléžka 
Date: Mon, Oct 17, 2016 at 9:27 PM
Subject: [ovirt-users] ovirt list's smtp on blacklist?
To: "us...@ovirt.org" 


Hello,

it looks like mailserver which serving us...@ovirt.org is on blacklist.

line from our smtp server log...

Oct 17 15:31:25 hermes postfix/smtpd[14082]: NOQUEUE: reject: RCPT from
lists.ovirt.org[2600:3c01::f03c:91ff:fe93:4b0d]: 554 5.7.1 Service
unavailable; Client host [2600:3c01::f03c:91ff:fe93:4b0d] blocked using
sbl.spamhaus.org; https://www.spamhaus.org/sbl/query/SBLCSS; from=<
users-boun...@ovirt.org> to= proto=ESMTP helo=<
lists.ovirt.org>


Cheers,
Jiri


___
Users mailing list
us...@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users




-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com




--
This message was sent by Atlassian JIRA
(v1000.456.2#100016)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra