Re: [systemd-devel] CentOS CI test suites failing

[František Šumšal]

The out-of-space issue seems to be resolved, for now, and the systemd CentOS CI 
script
should respect the (apparently) newly introduced rate-limiting machinery.
I went through the PRs updated in the last few hours and re-triggered all 
CentOS CI
jobs, so it now eating through the backlog. Given there's over 20 jobs to run,
it might take a good portion of the night (it's a midnight here), so please be 
patient :-)

I'll check the status once again in the morning and try to go through any 
unexpected
failures (hopefully there won't be any).

On 5/28/19 10:35 PM, František Šumšal wrote:
> This might take a little bit longer than anticipated, as the Jenkins slave 
> also ran
> out of space.
> 
> On 5/28/19 10:02 PM, František Šumšal wrote:
>> Hello!
>>
>> Thanks for the heads up. This was unfortunately caused by two simultaneous 
>> issues:
>>
>> 1) CentOS CI pool ran out of pre-installed machines
>> 2) I forgot to handle such situation in the systemd CentOS CI code :-)
>>
>> After giving the CentOS CI a few hours to get back on its tracks, I'll 
>> shortly
>> merge a patch[0] to handle it on the systemd side, and start slowly 
>> re-triggering
>> failed jobs for PRs.
>>
>> [0] https://github.com/systemd/systemd-centos-ci/pull/120
>>
>> On 5/28/19 8:39 PM, zach wrote:
>>> Looks like CentOS CI test suites are failing on multiple PRs with errors 
>>> like those listed below. Any advise on how to get these passing again or 
>>> who I could reach out to for help getting this back in order?
>>>
>>> 2019-05-28 16:04:26,307 [agent-control/] ERROR: Execution failed
>>> Traceback (most recent call last):
>>>   File "./agent-control.py", line 371, in 
>>> node, ssid = ac.allocate_node(args.version, args.arch)
>>>   File "./agent-control.py", line 82, in allocate_node
>>> jroot = json.loads(res)
>>>   File "/usr/lib64/python2.7/json/__init__.py", line 338, in loads
>>> return _default_decoder.decode(s)
>>>   File "/usr/lib64/python2.7/json/decoder.py", line 366, in decode
>>> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
>>>   File "/usr/lib64/python2.7/json/decoder.py", line 384, in raw_decode
>>> raise ValueError("No JSON object could be decoded")
>>> ValueError: No JSON object could be decoded
>>> Traceback (most recent call last):
>>>   File "./agent-control.py", line 449, in 
>>> ac.free_session(ssid)
>>> NameError: name 'ssid' is not defined
>>> mv: cannot stat ‘artifacts_*’: No such file or director 
>>>
>>>
>>> ___
>>> systemd-devel mailing list
>>> systemd-devel@lists.freedesktop.org
>>> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>>
>>
>>
>>
>> ___
>> systemd-devel mailing list
>> systemd-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>
> 
> 
> 
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> 


-- 
Frantisek Sumsal
GPG key ID: 0xFB738CE27B634E4B



signature.asc
Description: OpenPGP digital signature
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] CentOS CI test suites failing

[František Šumšal]

This might take a little bit longer than anticipated, as the Jenkins slave also 
ran
out of space.

On 5/28/19 10:02 PM, František Šumšal wrote:
> Hello!
> 
> Thanks for the heads up. This was unfortunately caused by two simultaneous 
> issues:
> 
> 1) CentOS CI pool ran out of pre-installed machines
> 2) I forgot to handle such situation in the systemd CentOS CI code :-)
> 
> After giving the CentOS CI a few hours to get back on its tracks, I'll shortly
> merge a patch[0] to handle it on the systemd side, and start slowly 
> re-triggering
> failed jobs for PRs.
> 
> [0] https://github.com/systemd/systemd-centos-ci/pull/120
> 
> On 5/28/19 8:39 PM, zach wrote:
>> Looks like CentOS CI test suites are failing on multiple PRs with errors 
>> like those listed below. Any advise on how to get these passing again or who 
>> I could reach out to for help getting this back in order?
>>
>> 2019-05-28 16:04:26,307 [agent-control/] ERROR: Execution failed
>> Traceback (most recent call last):
>>   File "./agent-control.py", line 371, in 
>> node, ssid = ac.allocate_node(args.version, args.arch)
>>   File "./agent-control.py", line 82, in allocate_node
>> jroot = json.loads(res)
>>   File "/usr/lib64/python2.7/json/__init__.py", line 338, in loads
>> return _default_decoder.decode(s)
>>   File "/usr/lib64/python2.7/json/decoder.py", line 366, in decode
>> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
>>   File "/usr/lib64/python2.7/json/decoder.py", line 384, in raw_decode
>> raise ValueError("No JSON object could be decoded")
>> ValueError: No JSON object could be decoded
>> Traceback (most recent call last):
>>   File "./agent-control.py", line 449, in 
>> ac.free_session(ssid)
>> NameError: name 'ssid' is not defined
>> mv: cannot stat ‘artifacts_*’: No such file or director 
>>
>>
>> ___
>> systemd-devel mailing list
>> systemd-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>
> 
> 
> 
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> 


-- 
Frantisek Sumsal
GPG key ID: 0xFB738CE27B634E4B



signature.asc
Description: OpenPGP digital signature
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] CentOS CI test suites failing

[František Šumšal]

Hello!

Thanks for the heads up. This was unfortunately caused by two simultaneous 
issues:

1) CentOS CI pool ran out of pre-installed machines
2) I forgot to handle such situation in the systemd CentOS CI code :-)

After giving the CentOS CI a few hours to get back on its tracks, I'll shortly
merge a patch[0] to handle it on the systemd side, and start slowly 
re-triggering
failed jobs for PRs.

[0] https://github.com/systemd/systemd-centos-ci/pull/120

On 5/28/19 8:39 PM, zach wrote:
> Looks like CentOS CI test suites are failing on multiple PRs with errors like 
> those listed below. Any advise on how to get these passing again or who I 
> could reach out to for help getting this back in order?
> 
> 2019-05-28 16:04:26,307 [agent-control/] ERROR: Execution failed
> Traceback (most recent call last):
>   File "./agent-control.py", line 371, in 
> node, ssid = ac.allocate_node(args.version, args.arch)
>   File "./agent-control.py", line 82, in allocate_node
> jroot = json.loads(res)
>   File "/usr/lib64/python2.7/json/__init__.py", line 338, in loads
> return _default_decoder.decode(s)
>   File "/usr/lib64/python2.7/json/decoder.py", line 366, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
>   File "/usr/lib64/python2.7/json/decoder.py", line 384, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> Traceback (most recent call last):
>   File "./agent-control.py", line 449, in 
> ac.free_session(ssid)
> NameError: name 'ssid' is not defined
> mv: cannot stat ‘artifacts_*’: No such file or director 
> 
> 
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> 


-- 
Frantisek Sumsal
GPG key ID: 0xFB738CE27B634E4B



signature.asc
Description: OpenPGP digital signature
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] CentOS CI test suites failing

[zach]

Looks like CentOS CI test suites are failing on multiple PRs with errors
like those listed below. Any advise on how to get these passing again or
who I could reach out to for help getting this back in order?

2019-05-28 16:04:26,307 [agent-control/] ERROR: Execution failed
Traceback (most recent call last):
  File "./agent-control.py", line 371, in 
node, ssid = ac.allocate_node(args.version, args.arch)
  File "./agent-control.py", line 82, in allocate_node
jroot = json.loads(res)
  File "/usr/lib64/python2.7/json/__init__.py", line 338, in loads
return _default_decoder.decode(s)
  File "/usr/lib64/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib64/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
Traceback (most recent call last):
  File "./agent-control.py", line 449, in 
ac.free_session(ssid)
NameError: name 'ssid' is not defined
mv: cannot stat ‘artifacts_*’: No such file or director
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] centos-ci

[Daniel Mack]

On 04/12/2016 01:52 PM, Jóhann B. Guðmundsson wrote:
> Anyone know that centos is not running the latest version(s) of systemd 
> required for the upstream bug tracker so one has to ask what 
> notification spam is this
> "Can one of the admins verify this patch?"

Regarding that spam, I already took measures against that.

I wasn't aware the CentOS CI started commenting on PRs, and neither was
anyone else on their side. The GitHub integration in the CentOS Jenkins
is brand new, we're their first user, so such things can happen. Sorry
about that.


Thanks,
Daniel
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] centos-ci

[Michal Sekletar]

On Tue, Apr 12, 2016 at 5:58 PM, Lennart Poettering
 wrote:

> The rhel-ci people offered us to use their spare machines, that's
> all. And Daniel took them up on it, and is now working on getting this
> hooked up.

It is not even rhel-ci (as in Red Hat internal), rather CentOS CI,
which is community service available to other free/open source
projects as well.

Michal

https://ci.centos.org/
https://fosdem.org/2016/schedule/event/centos_ci_getting_started/
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] centos-ci

[Lennart Poettering]

On Tue, 12.04.16 14:57, Jóhann B. Guðmundsson (johan...@gmail.com) wrote:

> >Right now the CI systems we use are all based on Ubuntu, which is
> >kinda weird, as most of the systemd core developers actually work for
> >RH and run Fedora locally... ;-)
> 
> I see but It's should not matter which company you work for or which
> distribution upstream developers favor otherwise you end up risking bias-ing
> the product on those favored downstream distribution or the (current)
> employment which is one of the root cause for the existing fragmentation in
> the first place.

we just want to test things on both major flavours of linux
distros. debian/ubuntu-style distros are nicely covered, and we'll
also have redhat/fedora-style distros covered with the rhel thing now.

With systemd we support quite a number of distros, and if we cover
those two flavours, then we should be in a pretty good state.

> And based on your response I have to ask, is someone higher up the Red hat
> ladder yanking your chain and thus the project loosing it's independence in
> the process or has your and other systemd's core developers view on the
> matter being independent changed?

Seriously, Johann? 

The rhel-ci people offered us to use their spare machines, that's
all. And Daniel took them up on it, and is now working on getting this
hooked up.

You completely misunderstand how Red Hat works...

In reality, I sometimes wished RH would provide us with more of
infrastructure services for systemd development. In fact though, we
pretty much never used any RH infrastructure. It's all github, fdo,
semaphore and the Ubuntu-ci stuff run by Canonical. In fact, Canonical
contributed more infrastructure to systemd development so far than RH
did.

Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] centos-ci

[Jóhann B . Guðmundsson]

On 04/12/2016 02:43 PM, Lennart Poettering wrote:

On Tue, 12.04.16 11:52, Jóhann B. Guðmundsson (johan...@gmail.com) wrote:


Anyone know that centos is not running the latest version(s) of systemd
required for the upstream bug tracker so one has to ask what notification
spam is this
"Can one of the admins verify this patch?"

Daniel is working on adding a CI infrastructure that allows us
building things on a RHEL-based system for each PR. This is work in
progress, and the spamming of the PRs with the mentioned line an
unfortunate mistake.

We have no intention to support upstream systemd on such old RHELs,
but the test systems are hacked enough with never packages to allow us
test things on Red-Hat-based systems.

Right now the CI systems we use are all based on Ubuntu, which is
kinda weird, as most of the systemd core developers actually work for
RH and run Fedora locally... ;-)


I see but It's should not matter which company you work for or which 
distribution upstream developers favor otherwise you end up risking 
bias-ing the product on those favored downstream distribution or the 
(current) employment which is one of the root cause for the existing 
fragmentation in the first place.


And based on your response I have to ask, is someone higher up the Red 
hat ladder yanking your chain and thus the project loosing it's 
independence in the process or has your and other systemd's core 
developers view on the matter being independent changed?


JBG
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] centos-ci

[Lennart Poettering]

On Tue, 12.04.16 11:52, Jóhann B. Guðmundsson (johan...@gmail.com) wrote:

> Anyone know that centos is not running the latest version(s) of systemd
> required for the upstream bug tracker so one has to ask what notification
> spam is this
> "Can one of the admins verify this patch?"

Daniel is working on adding a CI infrastructure that allows us
building things on a RHEL-based system for each PR. This is work in
progress, and the spamming of the PRs with the mentioned line an
unfortunate mistake.

We have no intention to support upstream systemd on such old RHELs,
but the test systems are hacked enough with never packages to allow us
test things on Red-Hat-based systems.

Right now the CI systems we use are all based on Ubuntu, which is
kinda weird, as most of the systemd core developers actually work for
RH and run Fedora locally... ;-)

Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] centos-ci

[Jóhann B . Guðmundsson]

Anyone know that centos is not running the latest version(s) of systemd 
required for the upstream bug tracker so one has to ask what 
notification spam is this

"Can one of the admins verify this patch?"

JBG
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel