Hi folks,
In another discussion, James Hunt raised the possibility of
periodically checking for runaway processes on Touch, killing those
consuming 100% CPU while creating a report to be sent to
https://errors.ubuntu.com.
I've summarised the key points of that discussion here into a
proposal. The
On 4 September 2013 12:25, Thomas Voß wrote:
> +1, the respective grace/timeout period would need to be determined
> from empirical data, too.
Agreed.
>> With the application lifecycle work, background applications will be
>> suspended and get no CPU time at all, so this check will only apply to
On 4 September 2013 16:22, Ted Gould wrote:
> We should probably start with reporting bugs, and then next step start
> killing. "Would have been killed" bugs might be an interesting metric :-)
Just to be pedantic: send error reports, not file bugs. Bugs can most
certainly be created from a probl
Stuart Langridge brought up an interesting idea for this on IRC, which
I'm copying here rather than having more side discussions:
(10:13:20) aquarius: ev, just reading your thread about runaway
processes on the touch mailing list (I'm not subscribed to the list,
so there's no good way of replying)
On 5 September 2013 18:35, Steve Langasek wrote:
>> Is this a proposal for 13.10?
>
> I think it's unrealistic to think anything discussed here would land for
> 13.10. We already have plenty of other things on our plate that are on the
> critical path for 13.10. :)
Agreed :)
> Anyway, point tak
On 12 September 2013 20:55, Mike McCracken wrote:
> In my experience, flashing the device with phablet-flash is not simple from
> within VBox because the VM will drop USB connection when the device reboots,
> then phablet-flash will time out.
You can add the device under USB Device Filters in the
Hi everyone,
Loïc asked me to clarify how you can retrace crashes on Touch devices
manually, since we're still waiting on armhf retracers to appear on
Prodstack.
You'll first need some apt sources for apport to download -dbg and
-dbgsym packages from. The configurations we use for the production
On 9 October 2013 19:45, Michał Sawicz wrote:
> On 09.10.2013 19:04, Evan Dandrea wrote:
>>
>> bzr branch lp:daisy
>
>
> FYI, I had to comment out saucy-updates and -security from ddebs in
> retracer/config/Ubuntu 13.10/armhf, and add corresponding deb-src for
> ap
This past Monday the Continuous Integration team started a rotation of
shifts as the vanguard in #ubuntu-ci-eng on Freenode and #ci on
Canonical IRC.
The person listed as the vanguard in the channel topic is on the hook
for answering your immediate questions about the CI infrastructure. If
you hav
Hi,
You may from time to time need things from the Continuous Integration
team. You have a few options:
1) For critical issues needing immediate attention, please continue to
ask the vanguard in #ci and #ubuntu-ci-eng.
2) For specific issues or needs from our infrastructure, please file a
bug he
f you
have questions, I'll happily hear them.
Thanks!
-- Forwarded message --
From: Larry Works
Date: 11 November 2013 08:12
Subject: Update on the lab
To: Evan Dandrea
Evan,
As you may have noticed (or very soon will) the lab is still down. The
day went far slower that we
bject: Lab update from 11 November
To: Evan Dandrea
Evan,
The networking configuration stopped shortly after the switches were
stacked and the link in was connected. Brian didn't like the way the
racks were populated and thought all of the CDUs needed to be flipped
endwise so the input po
ed message --
From: Larry Works
Date: 13 November 2013 14:22
Subject: Lab update from 12 November
To: Evan Dandrea
Greetings,
We have hardware up on the network. And, even better, it is reachable
via the VPN. We do still have a minor network issue getting the HP
managed switches tied into the r
Good morning everyone,
We are nearly there.
The Jenkins instance that used to reside at http://10.98.0.1:8080 is
now back up and running under http://d-jenkins.ubuntu-ci:8080. Some of
the other Jenkins systems are up (s-jenkins, q-jenkins, m-jenkins),
but without Jenkins running yet. We're still
Hello,
I just wanted to provide you with a quick update as Europe winds down
for the evening.
The phones are being delivered to 1SS by Rick as we speak and he's
going to spend the day wiring them up. As he needs to leave promptly
at 6pm today, there is a slight risk that all of the phones may not
In order to provide you with more predictable service from the CI
infrastructure, we're going to be sending notices of planned service
interruptions two days in advance of any work. The hope is that this
will give you adequate time to prepare and an opportunity to let us
know if the date overlaps w
This Tuesday, Wednesday, and Thursday, the EU-based members of the CI
team are meeting in Bluefin to train up on Juju.
We will continue to try to address your issues as quickly as is
feasible, but we will not have true vanguard coverage prior to 1300
UTC each of these days. If there is an emergenc
On 10 January 2014 09:15, Alexander Sack wrote:
> On Fri, Jan 10, 2014 at 6:23 AM, Paul Larson
> wrote:
>> = Mako =
>> 100% pass (no reruns for anything)
>> But we saw several crashes - dialer-app (which has been going on for a
>> while) as well as unity8 crash in default and in click-image-test
We're nearly finished transitioning the CI Train to a production
service. When and if issues arise, please direct them as follows:
- For the day-to-day operations of the CI Train, your point of contact
is the Landing Task Force. For example: if you need someone to
reconfigure a silo.
- For servic
On 23 June 2014 13:26, Alan Pope wrote:
> On Mon, Jun 23, 2014 at 12:10 PM, Alexander Sack wrote:
>> good that you ask this. We don't have that hooked into our process
>> yet, but are working on this as we speak. We basically have to first
>> get a view worked into errors.ubuntu.com that allows u
On 21 August 2014 17:19, Evan Dandrea wrote:
> The DCEs have been working hard on some improvements to our CI Lab
> network infrastructure. Most notably, they'll be normalising the VLAN
> numbering, moving inter-VLAN routing to batuan, and taking control of
> the remaining piec
21 matches
Mail list logo
