9:39 a.m.
Hi all,
Yesterday I worked on some change to otopi [1].
Changeset 3 failed jenkins.
Changeset 4 [2] succeeded, but was wrongly pushed to a somewhat-old parent.
Then I rebased locally and pushed again, changeset 5 [3].
In changeset 4, the version in master was 1.4.2-something.
After the rebase, the version was 1.5.0-something.
For some reason, changeset 5's build [3] built both 1.4.2- and 1.5.0- .
Any idea why? Some dirty environment?
Also, I now tried to run it again. I do not have a "retrigger" link,
so I tried using [4], input the changeset number, marked patchset 5,
pressed 'Trigger Selected', and now I see on the side:
Triggered Builds
54697,5
No jobs triggered for this event
Best,
[1] https://gerrit.ovirt.org/54697
[2] http://jenkins.ovirt.org/job/otopi_master_create-rpms-el7-x86_64_created/57/
[3] http://jenkins.ovirt.org/job/otopi_master_create-rpms-el7-x86_64_created/58/
[4] http://jenkins.ovirt.org/gerrit_manual_trigger/
--
Didi
2:11 p.m.
This is a multi-part message in MIME format.
--------------080809040501030806020302
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Hi,
Investigating a bit it does seems like dirty environment because I saw
in the console log that it had only build the 1.5.0*.src.rpm so it means
that the 1.4.2*.src.rpm were there before.
During the cleanup phase I can see the following:
*15:55:47 **Making sure there are no device mappings... **15:55:47 **Remo=
ving the used loop devices... **15:55:48 **losetup: invalid option -- 'D'=
**15:55:48 ****15:55:48 **Usage: **15:55:48 **losetup loop_device give i=
nfo **15:55:48 **losetup -a | --all list all used **15:55:48 **losetup -d=
| --detach <loopdev> [<loopdev> ...] delete **15:55:48 **losetup -f | --=
find find unused **15:55:48 **losetup -c | --set-capacity <loopdev> resiz=
e **15:55:48 **losetup -j | --associated <file> [-o <num>] list all assoc=
iated with
<file> **15:55:48 **losetup [ options ] {-f|--find|loopdev} <file> setup =
**15:55:48 ****15:55:48 **Options: **15:55:48 **-e | --encryption <type> =
enable data encryption with specified <name/num> **15:55:48 **-h | --help=
this help **15:55:48 **-o | --offset <num> start at offset <num> into fi=
le **15:55:48 **--sizelimit <num> loop limited to only <num> bytes of the=
file **15:55:48 **-p | --pass-fd <num> read passphrase from file descrip=
tor <num> **15:55:48 **-r | --read-only setup read-only loop device **15:=
55:48 **--show print device name (with -f <file>) **15:55:48 **-v | --ver=
bose verbose mode **15:55:48 ****15:55:48 ****15:55:48 **Usage: **15:55:4=
8 **losetup loop_device give info **15:55:48 **losetup -a | --all list al=
l used **15:55:48 **losetup -d | --detach <loopdev> [<loopdev> ...] delet=
e **15:55:48 **losetup -f | --find find unused **15:55:48 **losetup -c | =
--set-capacity <loopdev> resize **15:55:48 **losetup -j | --associated <f=
ile> [-o <num>] list all associated with
<file> **15:55:48 **losetup [ options ] {-f|--find|loopdev} <file> setup =
**15:55:48 ****15:55:48 **Options: **15:55:48 **-e | --encryption <type> =
enable data encryption with specified <name/num> **15:55:48 **-h | --help=
this help **15:55:48 **-o | --offset <num> start at offset <num> into fi=
le **15:55:48 **--sizelimit <num> loop limited to only <num> bytes of the=
file **15:55:48 **-p | --pass-fd <num> read passphrase from file descrip=
tor <num> **15:55:48 **-r | --read-only setup read-only loop device **15:=
55:48 **--show print device name (with -f <file>) **15:55:48 **-v | --ver=
bose verbose mode*
I think that this error interferes with the cleanup procedure. Am I wrong=
?
As for the retrigger link, I have no idea if it is missing on purpose or
should I fix that.
Can someone please assist?
Thanks
Gil
On 03/14/2016 09:39 AM, Yedidyah Bar David wrote:
Hi all,
Yesterday I worked on some change to otopi [1].
Changeset 3 failed jenkins.
Changeset 4 [2] succeeded, but was wrongly pushed to a somewhat-old par=
ent.
Then I rebased locally and pushed again, changeset 5 [3].
In changeset 4, the version in master was 1.4.2-something.
After the rebase, the version was 1.5.0-something.
For some reason, changeset 5's build [3] built both 1.4.2- and 1.5.0- .=
Any idea why? Some dirty environment?
Also, I now tried to run it again. I do not have a "retrigger" link,
so I tried using [4], input the changeset number, marked patchset 5,
pressed 'Trigger Selected', and now I see on the side:
Triggered Builds
54697,5
No jobs triggered for this event
Best,
[1] https://gerrit.ovirt.org/54697
[2] http://jenkins.ovirt.org/job/otopi_master_create-rpms-el7-x86_64_cr=
eated/57/
eated/58/
--------------080809040501030806020302
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
Investigating a bit it does seems like dirty environment because I
saw in the console log that it had only build the 1.5.0*.src.rpm so
it means that the 1.4.2*.src.rpm were there before.<br>
During the cleanup phase I can see the following:<br>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<pre class="console-output" style="box-sizing: border-box;
white-space: pre-wrap; word-wrap: break-word; margin: 0px; color: rgb(51, 51, 51);
font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: auto; text-align: start;
text-indent: 0px; text-transform: none; widows: 1; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255);"><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:47</span> </span></b><b>Making sure
there are no device mappings...
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:47</span> </span></b><b>Removing the
used loop devices...
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b>losetup:
invalid option -- 'D'
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b>
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b>Usage:
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> losetup
loop_device give info
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> losetup -a |
--all list all used
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> losetup -d |
--detach <loopdev> [<loopdev> ...] delete
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> losetup -f |
--find find unused
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> losetup -c |
--set-capacity <loopdev> resize
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> losetup -j |
--associated <file> [-o <num>] list all associated with
<file>
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> losetup [
options ] {-f|--find|loopdev} <file> setup
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b>
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b>Options:
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> -e |
--encryption <type> enable data encryption with specified
<name/num>
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> -h | --help
this help
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> -o | --offset
<num> start at offset <num> into file
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b>
--sizelimit <num> loop limited to only <num> bytes of the
file
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> -p | --pass-fd
<num> read passphrase from file descriptor <num>
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> -r |
--read-only setup read-only loop device
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> --show
print device name (with -f <file>)
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> -v | --verbose
verbose mode
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b>
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b>
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b>Usage:
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> losetup
loop_device give info
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> losetup -a |
--all list all used
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> losetup -d |
--detach <loopdev> [<loopdev> ...] delete
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> losetup -f |
--find find unused
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> losetup -c |
--set-capacity <loopdev> resize
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> losetup -j |
--associated <file> [-o <num>] list all associated with
<file>
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> losetup [
options ] {-f|--find|loopdev} <file> setup
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b>
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b>Options:
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> -e |
--encryption <type> enable data encryption with specified
<name/num>
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> -h | --help
this help
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> -o | --offset
<num> start at offset <num> into file
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b>
--sizelimit <num> loop limited to only <num> bytes of the
file
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> -p | --pass-fd
<num> read passphrase from file descriptor <num>
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> -r |
--read-only setup read-only loop device
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> --show
print device name (with -f <file>)
</b><b><span class="timestamp" style="box-sizing:
border-box;"><span style="box-sizing:
border-box;">15:55:48</span> </span></b><b> -v | --verbose
verbose mode</b></pre>
<br>
I think that this error interferes with the cleanup procedure. Am I
wrong?<br>
<br>
<br>
As for the retrigger link, I have no idea if it is missing on
purpose or should I fix that.<br>
Can someone please assist?<br>
<br>
Thanks<br>
Gil<br>
<br>
<br>
<div class="moz-cite-prefix">On 03/14/2016 09:39 AM, Yedidyah Bar
David wrote:<br>
</div>
<blockquote
cite="mid:CAHRwYXtbDzfo3o+ok_Eb-gu1q4_dvU9bOVujbaoVM2ziY9YRhg@mail.gmail.com"
type="cite">
<pre wrap="">Hi all,
Yesterday I worked on some change to otopi [1].
Changeset 3 failed jenkins.
Changeset 4 [2] succeeded, but was wrongly pushed to a somewhat-old parent.
Then I rebased locally and pushed again, changeset 5 [3].
In changeset 4, the version in master was 1.4.2-something.
After the rebase, the version was 1.5.0-something.
For some reason, changeset 5's build [3] built both 1.4.2- and 1.5.0- .
Any idea why? Some dirty environment?
Also, I now tried to run it again. I do not have a "retrigger" link,
so I tried using [4], input the changeset number, marked patchset 5,
pressed 'Trigger Selected', and now I see on the side:
Triggered Builds
54697,5
No jobs triggered for this event
Best,
[1] <a class="moz-txt-link-freetext"
href="https://gerrit.ovirt.org/54697">https://gerrit.ovirt.o...
[2] <a class="moz-txt-link-freetext"
href="http://jenkins.ovirt.org/job/otopi_master_create-rpms-el7-x86_...
[3] <a class="moz-txt-link-freetext"
href="http://jenkins.ovirt.org/job/otopi_master_create-rpms-el7-x86_...
[4] <a class="moz-txt-link-freetext"
href="http://jenkins.ovirt.org/gerrit_manual_trigger/">http:...
</pre>
</blockquote>
<br>
</body>
</html>
--------------080809040501030806020302--
2:30 p.m.
--9jHkwA2TBA/ec6v+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 03/14 14:11, Gil Shinar wrote:
Hi,
=20
Investigating a bit it does seems like dirty environment because I saw
in the console log that it had only build the 1.5.0*.src.rpm so it means
that the 1.4.2*.src.rpm were there before.
During the cleanup phase I can see the following:
=20
*15:55:47 **Making sure there are no device mappings... **15:55:47 **Remo=
ving the
used loop devices... **15:55:48 **losetup: invalid option -- 'D' *=
*15:55:48 ****15:55:48 **Usage: **15:55:48 **losetup loop_device give info =
**15:55:48 **losetup -a | --all list all used **15:55:48 **losetup -d | --d=
etach <loopdev> [<loopdev> ...] delete **15:55:48 **losetup -f | --find fin=
d unused **15:55:48 **losetup -c | --set-capacity <loopdev> resize **15:55:=
48 **losetup -j | --associated <file> [-o <num>] list all associated with
<file> **15:55:48 **losetup [ options ] {-f|--find|loopdev}
<file> setup =
**15:55:48 ****15:55:48 **Options: **15:55:48 **-e |
--encryption <type> en=
able data encryption with specified <name/num> **15:55:48 **-h | --help thi=
s help **15:55:48 **-o | --offset <num> start at offset <num> into file **1=
5:55:48 **--sizelimit <num> loop limited to only <num> bytes of the file **=
15:55:48 **-p | --pass-fd <num> read passphrase from file descriptor <num> =
**15:55:48 **-r | --read-only setup read-only loop device **15:55:48 **--sh=
ow print device name (with -f <file>) **15:55:48 **-v | --verbose verbose m=
ode **15:55:48 ****15:55:48 ****15:55:48 **Usage: **15:55:48 **losetup loop=
_device give info **15:55:48 **losetup -a | --all list all used **15:55:48 =
**losetup -d | --detach <loopdev> [<loopdev> ...] delete **15:55:48 **loset=
up -f | --find find unused **15:55:48 **losetup -c | --set-capacity <loopde=
v> resize **15:55:48 **losetup -j | --associated <file> [-o <num>] list
all=
associated with
<file> **15:55:48 **losetup [ options ] {-f|--find|loopdev}
<file> setup =
**15:55:48 ****15:55:48 **Options: **15:55:48 **-e |
--encryption <type> en=
able data encryption with specified <name/num> **15:55:48 **-h | --help thi=
s help **15:55:48 **-o | --offset <num> start at offset <num> into file **1=
5:55:48 **--sizelimit <num> loop limited to only <num> bytes of the file **=
15:55:48 **-p | --pass-fd <num> read passphrase from file descriptor <num> =
**15:55:48 **-r | --read-only setup read-only loop device **15:55:48 **--sh=
ow print device name (with -f <file>) **15:55:48 **-v | --verbose verbose m=
ode*
=20
=20
I think that this error interferes with the cleanup procedure. Am I wrong?
This issue should not be related to the dirty workspace, though it should be
fixed too (not critical or anything, happens because on el6 the losetup tool
does not have the -D option to free all the loop devices :/)
=20
=20
As for the retrigger link, I have no idea if it is missing on purpose or
should I fix that.
Can someone please assist?
About the triggers:
Project created events requires 2.12
=66rom http://jenkins.ovirt.org/gerrit-trigger/server/gerrit.ovirt.org/
:(, something is not ok there
=20
Thanks
Gil
=20
=20
On 03/14/2016 09:39 AM, Yedidyah Bar David wrote:
> Hi all,
>
> Yesterday I worked on some change to otopi [1].
>
> Changeset 3 failed jenkins.
>
> Changeset 4 [2] succeeded, but was wrongly pushed to a somewhat-old par=
ent.
>
> Then I rebased locally and pushed again, changeset 5 [3].
>
> In changeset 4, the version in master was 1.4.2-something.
>
> After the rebase, the version was 1.5.0-something.
>
> For some reason, changeset 5's build [3] built both 1.4.2- and 1.5.0- .
>
> Any idea why? Some dirty environment?
>
> Also, I now tried to run it again. I do not have a "retrigger" link,
> so I tried using [4], input the changeset number, marked patchset 5,
> pressed 'Trigger Selected', and now I see on the side:
>
> Triggered Builds
> 54697,5
> No jobs triggered for this event
>
> Best,
>
> [1] https://gerrit.ovirt.org/54697
> [2] http://jenkins.ovirt.org/job/otopi_master_create-rpms-el7-x86_64_cr=
eated/57/
eated/58/
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
--=20
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605
Email: dcaro(a)redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605
--9jHkwA2TBA/ec6v+
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJW5q7SAAoJEEBxx+HSYmnDktcH/jcuB/lo1GBeVKvquwAAmXNn
IQzWG6c3hAxsy9hYk+GHo/CWM+hrYRym8KDgGkSriQwLEhkNl53nd7dbq3uxhUrH
+EFmSaLvH7w+PHLFK+zbni01sKJ2EDsfBcRmnErbTRXzuhexibPhco/9GwTme5Ku
hBWTfmkOdfSulPFqRXpJPBHam8FXEHz2U2F7rP3cifCV2GBppFVHHTx7PIkaROsZ
k8j2Y5UP0wMxA9gU39J2rbd8KdMv9ujjZ7SgctYftlJ7TpYQF53WbJxk1K4MNFmy
bsCe4aiZ0gqcCQ6Keggt5SSsdFNz9jWnboytQceeYZ3pKxDPTtHx2RgHCAPLwGs=
=5DjV
-----END PGP SIGNATURE-----
--9jHkwA2TBA/ec6v+--
5:42 p.m.
Hi,
Pushed a patch that will add clean workspace before build starts. This
will solve the presence of old rpms under the workspace.
Downgraded the gerrit trigger plugin on the jenkins. That did added back
the retrigger link to the builds.
Thanks a lot, David.
Gil
On 03/14/2016 02:30 PM, David Caro wrote:
On 03/14 14:11, Gil Shinar wrote:
> Hi,
>
> Investigating a bit it does seems like dirty environment because I saw
> in the console log that it had only build the 1.5.0*.src.rpm so it means
> that the 1.4.2*.src.rpm were there before.
> During the cleanup phase I can see the following:
>
> *15:55:47 **Making sure there are no device mappings... **15:55:47 **Removing the
used loop devices... **15:55:48 **losetup: invalid option -- 'D' **15:55:48
****15:55:48 **Usage: **15:55:48 **losetup loop_device give info **15:55:48 **losetup -a |
--all list all used **15:55:48 **losetup -d | --detach <loopdev> [<loopdev>
...] delete **15:55:48 **losetup -f | --find find unused **15:55:48 **losetup -c |
--set-capacity <loopdev> resize **15:55:48 **losetup -j | --associated <file>
[-o <num>] list all associated with
> <file> **15:55:48 **losetup [ options ] {-f|--find|loopdev} <file> setup
**15:55:48 ****15:55:48 **Options: **15:55:48 **-e | --encryption <type> enable data
encryption with specified <name/num> **15:55:48 **-h | --help this help **15:55:48
**-o | --offset <num> start at offset <num> into file **15:55:48 **--sizelimit
<num> loop limited to only <num> bytes of the file **15:55:48 **-p | --pass-fd
<num> read passphrase from file descriptor <num> **15:55:48 **-r | --read-only
setup read-only loop device **15:55:48 **--show print device name (with -f <file>)
**15:55:48 **-v | --verbose verbose mode **15:55:48 ****15:55:48 ****15:55:48 **Usage:
**15:55:48 **losetup loop_device give info **15:55:48 **losetup -a | --all list all used
**15:55:48 **losetup -d | --detach <loopdev> [<loopdev> ...] delete **15:55:48
**losetup -f | --find find unused **15:55:48 **losetup -c | --set-capacity <loopdev>
resize **15:55:48 **losetup -j | --associated <file> [-o <num>] list all
associated with
> <file> **15:55:48 **losetup [ options ] {-f|--find|loopdev} <file> setup
**15:55:48 ****15:55:48 **Options: **15:55:48 **-e | --encryption <type> enable data
encryption with specified <name/num> **15:55:48 **-h | --help this help **15:55:48
**-o | --offset <num> start at offset <num> into file **15:55:48 **--sizelimit
<num> loop limited to only <num> bytes of the file **15:55:48 **-p | --pass-fd
<num> read passphrase from file descriptor <num> **15:55:48 **-r | --read-only
setup read-only loop device **15:55:48 **--show print device name (with -f <file>)
**15:55:48 **-v | --verbose verbose mode*
>
>
> I think that this error interferes with the cleanup procedure. Am I wrong?
This issue should not be related to the dirty workspace, though it should be
fixed too (not critical or anything, happens because on el6 the losetup tool
does not have the -D option to free all the loop devices :/)
>
> As for the retrigger link, I have no idea if it is missing on purpose or
> should I fix that.
> Can someone please assist?
About the triggers:
Project created events requires 2.12
from http://jenkins.ovirt.org/gerrit-trigger/server/gerrit.ovirt.org/
:(, something is not ok there
> Thanks
> Gil
>
>
> On 03/14/2016 09:39 AM, Yedidyah Bar David wrote:
>> Hi all,
>>
>> Yesterday I worked on some change to otopi [1].
>>
>> Changeset 3 failed jenkins.
>>
>> Changeset 4 [2] succeeded, but was wrongly pushed to a somewhat-old parent.
>>
>> Then I rebased locally and pushed again, changeset 5 [3].
>>
>> In changeset 4, the version in master was 1.4.2-something.
>>
>> After the rebase, the version was 1.5.0-something.
>>
>> For some reason, changeset 5's build [3] built both 1.4.2- and 1.5.0- .
>>
>> Any idea why? Some dirty environment?
>>
>> Also, I now tried to run it again. I do not have a "retrigger" link,
>> so I tried using [4], input the changeset number, marked patchset 5,
>> pressed 'Trigger Selected', and now I see on the side:
>>
>> Triggered Builds
>> 54697,5
>> No jobs triggered for this event
>>
>> Best,
>>
>> [1] https://gerrit.ovirt.org/54697
>> [2] http://jenkins.ovirt.org/job/otopi_master_create-rpms-el7-x86_64_created/57/
>> [3] http://jenkins.ovirt.org/job/otopi_master_create-rpms-el7-x86_64_created/58/
>> [4] http://jenkins.ovirt.org/gerrit_manual_trigger/
> _______________________________________________
> Infra mailing list
> Infra(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
3176
days inactive
3176
days old
3 comments
3 participants
participants (3)
-
David Caro -
Gil Shinar -
Yedidyah Bar David