/me hugs apw
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777646
Title:
bcmwl 6.30.223.271+bdcom-0ubuntu1~1.2 ADT test failure with linux-hwe-
edge 4.15.0-23.25~16.04.1
To manage notifications
> The proposed fix installed successfully and the problem is corrected.
\o/
Yet:
> I have run into a bug when installing the 4.15.0-29-generic kernel
today.
So can we have the -proposed fix landed ?
Pretty please ? With sugar on top ?
Is it a matter of changing one bug tag ?
Which one (verifi
Same here (broadcom-sta vs bcmwl).
Can a kind soul explains if one can be used instead of the other and
why/how they differ ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757008
Title:
Broadcom w
Happened today after the upgrade, lost wifi :-/
Linux pump 4.15.0-24-generic #26~16.04.1-Ubuntu SMP Fri Jun 15 14:35:08
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
rebooting with an older kernel worked around the issue:
Linux pump 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27
UTC 2018
Happened today after the upgrade, lost wifi :-/
Linux pump 4.15.0-24-generic #26~16.04.1-Ubuntu SMP Fri Jun 15 14:35:08
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Yeah, there is a significant overlap between scw-generate-network-config and
cloud-init here.
I think it makes sense to align both approaches ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775086
I created another instance and did 'systemctl --no-pager disable scw-
generate-net-config' before installing cloud-init.
2 reboots later and things are still fine.
I think that counts as a workaround but I don't know systemd enough to
decide if someone is wrong here :-/
root@image-builder-scw-a
** Attachment added: "list-dependencies.txt"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1775086/+attachment/5148786/+files/list-dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
systemctl status cloud-init.service
● cloud-init.service - Initial cloud-init job (metadata service crawler)
Loaded: loaded (/lib/systemd/system/cloud-init.service; enabled; vendor
prese Active: inactive (dead)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
root@image-builder-scw-amd64:~# systemctl --no-pager status cloud-init.service
● cloud-init.service - Initial cloud-init job (metadata service crawler)
Loaded: loaded (/lib/systemd/system/cloud-init.service; enabled; vendor
preset: enabled)
Active: inactive (dead)
--
You received this bug
> user_data.txt: Error: [Errno 2] No such file or directory:
'/var/lib/cloud/instance/user-data.txt'
Fallout from /var/lib/cloud/instance being a dir rather than a symlink.
I empirically understood that this is caused by
cloudinit.util.write_file calling ensure_dir()
--
You received this bug no
Public bug reported:
As discussed on IRC, installing cloud-init and rebooting a xenial
instance fails.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cloud-init 18.2-4-g05926e48-0ubuntu1~16.04.2
Uname: Linux 4.4.127-mainline-rev1 x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
@Bryan: Hi !
Well, it's up to Canonical to decide whether they want to depend on the
community to maintain a tool that is/was used for Canonical internal
projects (or finally plan to migrate away from it).
I can't speak for breezy devs as I'm not involved (enough) there nor can
I speak for Canoni
** Changed in: bzr
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606203
Title:
Failed to build of snappy package on Launchpad: Invalid header value
'B
ssh support works, most remote uses rely on it.
I'm not sure I'm reading the traceback correctly but I would guess the
issue is that you're providing the key password when your ring password
is expected (which would give access to the key).
So, not really a bzr issue even if the error message cou
Short answer: neither the xenial nor the yaketti branches where created
on launchpad so the importer can't keep them up to date.
If you're the package maintainer, you're free to create those branches
though
** Package changed: bzr (Ubuntu) => udd
--
You received this bug notification because yo
bzr refuses to handle files containing '/' or '\'.
For the "C:\nppdf32Log\debuglog.txt" case, on ubuntu, that seems legit,
this is a windows path and attempting to checkout that file on a windows
system will be problematic.
For the "systemd/system/snaps-cap\x2dtest.sideload-LSXRFfhCCLCY.mount" c
/o\ but how come paramiko breaking backwards compatibility entered
xenial ?
See https://bugs.launchpad.net/bzr/+bug/1579093
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592731
Title:
bzr fails to
*** This bug is a duplicate of bug 1579093 ***
https://bugs.launchpad.net/bugs/1579093
** This bug has been marked a duplicate of bug 1579093
TypeError: prefetch() takes exactly 2 arguments (1 given)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
> Well, the way it works is we need to demote everything that depends
/build-depends on python2 first. But yes, the goal is for it to be
demoted for 18.04 but that is a stretch goal - so waiting is certainly
an option.
Pfew, what a relief ;-D
> Moving from Main to Universe does not (at least in m
** Changed in: bzr
Importance: Medium => Undecided
** Changed in: bzr
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/826962
Title:
bzr crashed with ValueErr
> Bazaar development is in maintenance mode and there are not resources
to port it to python 3.
I'm been "maintaining" bzr for the last years being perfectly aware that
the python3 support was important.
I'm a bit surprised to find this bug as the first contact with the
bazaar project but let's s
> If you are starting a new project you really want to use git (yes, that is
> technically just my opinion).
<...>
> This is not reach for archive action yet, I just wanted to start the
> discussion here.
I'm not sure that's the right tone to start this discussion ;-)
So instead of following th
Public bug reported:
http://people.canonical.com/~ubuntu-archive/proposed-
migration/update_output.txt mentions loggerhead as blocking bzr 2.7.0
promotion.
The attached patch has will be sent to debian and bump the versionized
dependency.
** Affects: loggerhead (Ubuntu)
Importance: Undecid
Public bug reported:
http://people.canonical.com/~ubuntu-archive/proposed-
migration/update_output.txt mentions bzr-upload as blocking bzr 2.7.0
promotion.
The attached patch has been sent to debian and bump the versionized
dependency.
** Affects: bzr-upload (Ubuntu)
Importance: Undecided
Jelmer confirmed he was running from sources.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545785
Title:
bzrtools blocking bzr-2.7.0 promotion
To manage notifications about this bug go to:
https:
Previous version of the patch missed bumping maximum_bzrlib_version to
avoid the compatibility warning.
** Patch removed: "bzr-pipeline-1.5-2.patch"
https://bugs.launchpad.net/ubuntu/+source/bzr-pipeline/+bug/1545787/+attachment/4572212/+files/bzr-pipeline-1.5-2.patch
** Patch added: "bzr-pip
@Jelmer: What's your context exactly ? debian removes all the code
associated with the version checks and ubuntu carry the same patch.
Are you running from source maybe ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Public bug reported:
http://people.canonical.com/~ubuntu-archive/proposed-
migration/update_excuses.html mentions bzr-pipeline as blocking bzr
2.7.0 promotion.
The attached patch has been sent to debian and bump the versionized
dependency.
** Affects: bzr-pipeline (Ubuntu)
Importance: Undec
Public bug reported:
http://people.canonical.com/~ubuntu-archive/proposed-
migration/update_excuses.html mentions bzrtools as blocking bzr 2.7.0
promotion.
The attached patch has been sent to debian and bump the versionized
dependency.
** Affects: bzrtools (Ubuntu)
Importance: Undecided
Public bug reported:
debian unstable now carries bzr-2.7.0-2
The attached patch was built from MOM
** Affects: bzr (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "patch abive bzr-2.7.0-2"
https://bugs.launchpad.net/bugs/1544487/+attachment/4569205/+files/bzr-2
** Changed in: bzr
Milestone: None => 2.7b1
** Changed in: bzr
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480015
Title:
Test failure: hexify remov
Please don't mess up bug statuses if you're not involved in fixing them.
** Changed in: bzr
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469495
Title:
mak
** Changed in: bzr
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469495
Title:
make man respond to bzr subcommands
To manage notifications about this bug g
** Changed in: bzr (Ubuntu)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/661678
Title:
bzr whoami: unable to copy ownership from '$HOME/.bazaar' to
'$HOM
It never happened again (and may have been a misuse involving immortal
sudo subprocesses but I'm blurry on the details), marking invalid but
fixed released may be correct as well.
** Changed in: lxc (Ubuntu)
Status: Expired => Invalid
--
You received this bug notification because you are
** Changed in: bzr
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451448
Title:
bzr fails to build on vivid (release) and trusty (test-rebuild only)
To ma
For the record, on a wily system, there is still a dependency loop
involving open-iscsi but system can still boot successfully.
Roughly, I can do:
# apt-get install open-iscsi
# iscsi_discovery
and see the expected volumes
But rebooting from there causes the dependency loop and open-iscsi is
n
/var/log/dist-upgrade/apt-clone_system_state.tar.gz
** Attachment added: "apt-clone_system_state.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1504897/+attachment/4500901/+files/apt-clone_system_state.tar.gz
--
You received this bug notification because you are a member of
** Attachment added: "apt-term.log"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1504897/+attachment/4500902/+files/apt-term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504897
T
I got the error today on upgrade 15.04 -> 15.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1476010
Title:
package nfs-common 1:1.2.8-9ubuntu8.1 failed to install/upgrade:
subprocess installed
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23775778 seems to be
related.
How far is ubuntu from debian on this precise topic ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1465196
Title:
o
I ran into that bug again now that I really need open-iscsi ;)
I'm using systemd on vivid.
I want to mount remote disks but I don't want to boot from one.
s/remote_fs/local_fs/ in /etc/init.d/open-iscsi doesn't seem to be
enough :-/
Purging open-iscsi (and removing the mount from fstab) was the
** Changed in: bzr
Assignee: (unassigned) => Vincent Ladeuil (vila)
** Changed in: bzr
Status: Confirmed => In Progress
** Changed in: bzr
Milestone: None => 2.7b1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
@Chris: Thanks !
I had to implement a different scheme not using nested containers but
still requiring lxc-1.1.2.
I'll give nested containers another shot asap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
@Chris: Where do you add the ubuntu-lxc/daily ppa ? On the host or on
the outer container ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1436723
Title:
Regression: Nested LXC is broken on Vivid
To
I run into the same issue on a vivid host while trying to start a trusty
nested container from inside a trusty container.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1436723
Title:
Regression: Nes
Sorry for the reply delay :-/
I've been able to reproduce on vivid.
These tests are racy (yet another occurrence of running a TCP server and
client in the same process (different threads)).
Out of the ~800 http tests, those two ones are the simplest: they
connect to an http server that always re
** Also affects: bzr
Importance: Undecided
Status: New
** Changed in: bzr
Status: New => Confirmed
** Changed in: bzr
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
FWIW, I also felt into related traps and I have not encounter a use case
for multiple test arguments. So +1 to have a single one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453509
Title:
simplif
Ack, thanks for the explanation !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454735
Title:
adt-run doesn't realize the phone is not rebooting
To manage notifications about this bug go to:
https
Hmm, sorry for the late reaction but, is the 'sleep 3' still needed now
that the subprocess is not killed by the ssh kill wrapper ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454735
Title:
adt-r
Thanks for the explanation, makes sense !
Confirmed it works now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454735
Title:
adt-run doesn't realize the phone is not rebooting
To manage notifica
> So when exactly did you see the regression?
When I tried to re-run the test in https://code.launchpad.net
/~canonical-platform-qa/unity8/1421009-hangs-on-boot/ with 3.14.1
I *tried* to come back to a working version, both on autopkgtest itself
and and phones, using older images, but couldn't fi
=== modified file 'lib/VirtSubproc.py'
--- lib/VirtSubproc.py 2015-05-11 08:39:02 +
+++ lib/VirtSubproc.py 2015-05-14 10:07:42 +
@@ -328,7 +328,7 @@
adtlog.info('state saved, waiting for testbed to reboot...')
else:
execute_timeout(None, 30,
-
Forgot to mention that both runs were against a mako devel-proposed/195
with a unity8 update in the overlay ppa.
Re-running with image 196 on mako (with the up-to-date unity8) exhibit
the same issues for both 3.14 and 3.13.
The same issue occurs with krillin devel-proposed/210.
If I adb shell to
** Attachment added: "log for 3.13"
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1454735/+attachment/4396868/+files/log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454735
Title:
With 3.13 the error is different:
~/qa/autopkgtest/3.13/run-from-checkout -d -B --unbuilt-tree . -o
~/ci/unity8/results-$(date +%Y-%m-%d-%H-%M) --- ssh -s adb -- -p
--serial 04f55a0bc855b2bc
ends with:
adt-run: DBG: testbed command exited with code 0
adt-run [16:59:47]: test process request
Public bug reported:
>From https://code.launchpad.net/~canonical-platform-qa/unity8/1421009
-hangs-on-boot/
Running:
adt-run -d -B --unbuilt-tree . -o ~/ci/unity8/results-$(date +%Y-%m-%d-%H-%M)
--- ssh -s adb -- -p --serial 04f55a0bc855b2bc
happily proceed without the phone rebooting a
While the emulator is created, the log mentions:
[4.295252] init: cannot find '/sbin/adbd', disabling 'adbd'
But once the emulator is started and the developer mode turned on
through the UI, adbd can be found under /usr/bin
--
You received this bug notification because you are a member of U
I can't reproduce this anymore :-/
I did re-flash the phone and followed the same process to configure a
silo, add -d to both adt-run and adt-virt-ssh, but no luck.
My best guess at this point is that it may have been caused by a space
issue on the phone...
I'll leave the bug incomplete so it'll
Like https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1449446
I can't reproduce this bug anymore.
Again, best guess is a space issue on the phone.
Marking incomplete.
** Changed in: autopkgtest (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because yo
Test defined in https://code.launchpad.net/~canonical-platform-
qa/unity8/1421009-hangs-on-boot/+merge/257408
Corrupted log: doh, I asked lp to attach the file produced by adt...
/me scratches head
Oh right, lp display is broken, if you download the file it's fine (a
couple of ^M may explain lp
FTR before I switch to something else: happened again at 6th reboot
(without ssh -d).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1449431
Title:
sudo password loss ?
To manage notifications about
Public bug reported:
I encountered the following while trying to better debug
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1449431
Adding '-d' to adt-virt-ssh breaks (log attached) with:
adt-run [11:13:05]: ERROR: unexpected error: failed to run apt-get to
satisfy adt-satdep.deb de
Re-running with:
adt-run -U -B --unbuilt-tree . -o ../results-$(date +%Y-%m-%d-%H-%M) ---
ssh -d -s adb -- -p
i.e. --- ssh *-d* leads to:
adt-run [11:13:05]: ERROR: unexpected error: failed to run apt-get to satisfy
adt-satdep.deb dependencies
** Attachment added: "ssh -d breaks -U ?"
Public bug reported:
Weird failure encountered with https://code.launchpad.net/~canonical-
platform-qa/unity8/1421009-hangs-on-boot/+merge/257408
I first saw it after 5 reboots and then after 13 reboots (log with -d
attached).
I.e. the sudo password is available for previous reboots but suddenly
Public bug reported:
I've been using adt-run with various options and missing the command-
line invocation in the 'results/log' makes it harder to analyse/compare
different runs.
It already does log its version number which is nice and should be kept
;)
Additional brownie points if the logged co
@Pat: Can you re-try adding '-d' to your adt-run options and share the
log ?
/tmp/autopkgtest-reboot is created by adt-run on the testbed at run
time.
I'm eager to learn how such a failure can happen and where it needs to
be fixed.
--
You received this bug notification because you are a member
@Pat: Just in case, I'm on vivid and use autopkgtest 3.13, that may be
related.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
To manage notifications a
Also reproduced on arale with the branch above after 25 reboots.
$ adb shell system-image-cli -i
current build number: 22
device name: arale
channel: ubuntu-touch/arale-vivid-proposed
last update: 2010-01-01 00:29:22
version version: 22
version ubuntu: 30e975dd988b3be7886017b6d46b2821da187d7b8e5e4
** Branch linked: lp:~canonical-platform-qa/unity8/1421009-hangs-on-boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
To manage notifications about th
I've created https://code.launchpad.net/~canonical-platform-
qa/unity8/1421009-hangs-on-boot/+merge/257408 to reproduce this bug.
Given the last comment above it may need to be tweaked s/30/60/ .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Building on top of the added test (test_cloud_config_archive), using the
following breaks (the yaml can't be parsed):
message = '''#cloud-config-archive
- content: "#cloud-config\napt_update: true\napt_upgrade: true\nchpasswd:\n
expire:\
\ false\nmanage_etc_hosts: true\npacka
** Package changed: snappy (Ubuntu) => snappy-ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1443557
Title:
snappy update error message 'already locked' is confusing
To manage notifications a
Public bug reported:
Running 'snappy update' may issue an 'already locked' error message.
mvo explained that this is caued by 'autopilot' running in the
background and 'tail /var/log/syslog' contains more details (indeed it
does).
The message is confusing for a newcomer.
** Affects: snappy (Ubu
Re-creating the symlink with the command above was enough to fix the
issue for me.
Thanks !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1430675
Title:
fails to set up a bridged network interface
In a different run, still same adt version http://d-jenkins.ubuntu-
ci:8080/job/vivid-boottest-language-pack-touch-it/1/console there is
only:
16:52:41 E: ERROR: timed out waiting for Unity greeter
16:52:41 E: : failure: setup script failed with code 1:
/usr/share/autopkgtest/ssh-setup/adb open -
> That's all the lines with "adt-run: DBG: "
Bah, of course, thanks for the reminder ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423497
Title:
timed out waiting for Unity greeter can be clear
> Which autopkgtest version do you have?
adt-run is helpfully providing this ;) :
08:16:39 E: adt-run [08:16:39]: version 3.9.6-0~1054~ubuntu14.04.1
08:16:39 E: + timeout 600 adt-run --debug --no-built-binaries --unbuilt-
tree /var/lib/jenkins/slaves/krillin-09/workspace/vivid-boottest-wayland
/
Public bug reported:
http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-wayland/1/console
failed.
This is the expected behavior.
The output may be clearer if the following wasn't shown:
08:24:55 E: ERROR: timed out waiting for Unity greeter
08:24:56 E: sudo: /tmp/adt-run-wrapper: command not fo
Public bug reported:
http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-ubuntu-
keyboard/3/console has the whole log.
That was with devel-proposed/krillin/version-109.tar.xz.
It seems the phone boots properly, yet, ssh connection can't be
established.
Re-running the job with devel-proposed/kril
http://d-jenkins.ubuntu-ci:8080/view/Vivid/view/BootTest/job/vivid-boottest-unity-scopes-api/1/console
looks similar but I have a traceback (running with -d helps ?):
FailedConsole Output
Started by remote host 10.100.0.2
Building remotely on krillin-09 in workspace
/var/lib/jenkins/sla
Public bug reported:
http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-ubuntu-ui-
toolkit/1/console
09:38:02 E: adt-run [09:38:02]: test getpkgsrc: - - - - - - - - - - results -
- - - - - - - - -
09:38:02 O: getpkgsrcPASS
09:38:02 E: adt-run: DBG: sending command to testbed: copyup
http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-lxc/2/console has the
same issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1420355
Title:
adt-run bombs for a test that passed
To manage noti
Same here, I need to disable wifi to be able to send MMS from Free
Mobile.
Also, I can't receive MMS, with and without wifi (people have tried to
send me some 4 hours ago).
** Changed in: nuntium (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a me
Right, no need to further debug timeout/adt-run bad interactions indeed.
The initial need was to make sure adt-run will always timeout. If we
have a way to do that while all missing timeouts are added to adt-run
(if some are still missing...), we're good.
--
You received this bug notification be
Public bug reported:
$ mkdir tmp
$ adt-buildvm-ubuntu-cloud -v -r vivid
$ bzr branch lp:~canonical-ci-engineering/ubuntu-test-cases/boottest
$ export ADT_VIRT="adt-virt-qemu ./adt-vivid-amd64-cloud.img"
$ boottest/scripts/boottest.sh vivid libpng
This ends with:
adt-run [15:40:11]: version 3.
Public bug reported:
Encountered when trying to test that a phone image upgraded with
-proposed still boots.
According to pitti:
naming it initrd.img-touch is broken, that's not what initramfs-tools and other
tools expect
so at the very least, i-t-ubuntu-touch needs to disable the trigger someh
Public bug reported:
>From fginther:
Experimenting with a test known to fail the reboot on the phone, 'apt-
get remove -y --force-yes lxc'.
adt-run does not timeout by default in a short enough time period.
Experimenting now with setting specific values:
--timeout-test=300 : adt-run did not
** Changed in: bzr (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381004
Title:
bzr hangs on commit while "Uploading data to master branch" using SFTP
To m
> Upgraded to Vivid, my bazaar.conf contains the letter "é".
Any details about which config option value contains that ? 'email' ?
** Changed in: bzr (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
Upgraded to Vivid, my bazaar.conf contains the letter "é".
Most bzr commands now fail with UnicodeDecodeError in bzrlib/rio.py
+
+ bzr 2.7.0dev1 on python 2.7.8 (Linux-3.16.0-24-generic-x86_64-with-
+ Ubuntu-15.04-vivid)
+ arguments: ['/usr/bin/bzr', 'init']
+ plug
Public bug reported:
$ adt-run --output-dir results .// --setup-commands='apt-get update' ---
lxc -es adt-utopic
...
adt-run [15:13:25]: unbuilt-tree .//
Unexpected error:
Traceback (most recent call last):
File "/usr/share/autopkgtest/python/VirtSubproc.py", line 671, i
*** This bug is a duplicate of bug 1314274 ***
https://bugs.launchpad.net/bugs/1314274
@Christopher, sorry had a tab opened (but never came back to it) to
confirm I'm now running 3.13.0-32-generic #57-Ubuntu which includes the
fix and I didn't encounter the bug anymore (while still heavily usi
I'm testing the kernel mentioned in bug #1314274 as this bug seems to be
a duplicate, will mark it as such if I don't get a crash in the next
days.
Note that I had to
http://www.ubuntuupdates.org/package/canonical_kernel_team/trusty/main/base
/linux-headers-3.13.0-31 in addition to the packages pr
Just occurred again and indeed that was when running 'juju destroy-
environment lxc --force'
The only thing that is not standard in my config is that I'm using an
existing 'br0' bridge in /etc/lxc/default.conf (lxc.network.link = br0)
and I disable /etc/default/lxc-net with (USE_LXC_BRIDGE="false"
FTR, issuing 'juju destroy-environment lxc --force' after the reboot
completes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336859
Title:
crash without any trace in log files
To manage notificat
Public bug reported:
This is the second time (unclear about a third one) I encounter this
crash and all I could do was power-cycling to reboot.
/var/crash is empty
/var/log/syslog and /var/log/kern.log don't contain any hint around the
crash time (the subsequent reboot is present though).
So I
** Package changed: bzr (Ubuntu) => bzr-webdav (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953154
Title:
bzr crashed with TypeError in __init__(): __init__() got an unexpected
keyword a
1 - 100 of 496 matches
Mail list logo
