Bug#903441: dgit: autopkgtest failures in Ubuntu [and 1 more messages]
On Fri, Jul 13, 2018 at 06:22:43PM +0100, Ian Jackson wrote:
> Ian Jackson writes ("Re: Bug#903441: dgit: autopkgtest failures in Ubuntu
> [and 1 more messages]"):
> > Sorry, this is due to #903696 in autopkgtest, which I just filed. I
> > should have CC'd you.
> >
> > 5.9+exp4 is supposed to fix it. This time, for sure.
>
> Wow! It actually DTRT! Please do let me know whether it fixes the
> symptoms, in Ubuntu, of my incorrect dch invocations.
It does, and now autopkgtests pass on Ubuntu! :D
5.9+exp4 landed successfully in the release pocket afterwards :)
Thank you!
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
Bug#903441: dgit: autopkgtest failures in Ubuntu [and 1 more messages]
Ian Jackson writes ("Re: Bug#903441: dgit: autopkgtest failures in Ubuntu [and
1 more messages]"):
> Sorry, this is due to #903696 in autopkgtest, which I just filed. I
> should have CC'd you.
>
> 5.9+exp4 is supposed to fix it. This time, for sure.
Wow! It actually DTRT! Please do let me know whether it fixes the
symptoms, in Ubuntu, of my incorrect dch invocations.
Regards,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#903441: dgit: autopkgtest failures in Ubuntu [and 1 more messages]
Mattia Rizzolo writes ("Re: Bug#903441: dgit: autopkgtest failures in Ubuntu
[and 1 more messages]"):
> Doesn't look like it's enough, ci.d.n still fails due to:
> |cp: cannot overwrite directory
> '/tmp/tmp.ugPG6m6qcG/autopkgtest-incoming/unstable/amd64/d/dgit/601985/artifacts/example/.git'
> with non-directory
> |tar: ./example/.git: Cannot open: File exists
Sorry, this is due to #903696 in autopkgtest, which I just filed. I
should have CC'd you.
5.9+exp4 is supposed to fix it. This time, for sure.
Ian.
Bug#903441: dgit: autopkgtest failures in Ubuntu [and 1 more messages]
On Fri, Jul 13, 2018 at 12:56:06AM +0100, Ian Jackson wrote:
> Ian Jackson writes ("Re: Bug#903441: dgit: autopkgtest failures in Ubuntu
> [and 1 more messages]"):
> > This is now implemented in 5.9+exp1, just uploaded to Debian
> > experimental. Can you give it a try in Ubuntu please ?
>
> This trips what seems to be a bug in adt-virt-lxc; see #903680
> and https://ci.debian.net/packages/d/dgit/unstable/amd64/.
>
> 5.9+exp3 (just uploaded) has what I think is the fix.
Doesn't look like it's enough, ci.d.n still fails due to:
|cp: cannot overwrite directory
'/tmp/tmp.ugPG6m6qcG/autopkgtest-incoming/unstable/amd64/d/dgit/601985/artifacts/example/.git'
with non-directory
|tar: ./example/.git: Cannot open: File exists
|tar: Exiting with failure status due to previous errors
|: failure: copyup destination failed, status 2
|autopkgtest [08:52:33]: ERROR: testbed failure: cannot send to testbed: [Errno
32] Broken pipe
For what concerns ubuntu, I synced the experimental version, and at
least armhf, ppc64el and s390x finished the tests, but started again
right after (within publishing their results to autopkgtest.u.c,
probably they are available in swift somewhere but I wouldn't know where
to look without loading the huge index); makes me think of the same bug.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
Bug#903441: dgit: autopkgtest failures in Ubuntu [and 1 more messages]
Ian Jackson writes ("Re: Bug#903441: dgit: autopkgtest failures in Ubuntu [and
1 more messages]"):
> This is now implemented in 5.9+exp1, just uploaded to Debian
> experimental. Can you give it a try in Ubuntu please ?
This trips what seems to be a bug in adt-virt-lxc; see #903680
and https://ci.debian.net/packages/d/dgit/unstable/amd64/.
5.9+exp3 (just uploaded) has what I think is the fix.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#903441: dgit: autopkgtest failures in Ubuntu [and 1 more messages]
Ian Jackson writes ("Re: Bug#903598: devscripts: dch -r [something]"):
> Mattia Rizzolo writes ("Re: Bug#903598: devscripts: dch -r [something]"):
> > Ton of things use '' (i.e. empty string). Including debchange's
> > testsuite :3
>
> Well, that's helpful information, indeed. I will do the same :-).
This is now implemented in 5.9+exp1, just uploaded to Debian
experimental. Can you give it a try in Ubuntu please ?
I have also made use of AUTOPKGTEST_ARTIFACTS and I would like to know
if this output is too large.
Thanks,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#903441: dgit: autopkgtest failures in Ubuntu
Mattia Rizzolo writes ("Re: Bug#903441: dgit: autopkgtest failures in Ubuntu"):
> On Wed, Jul 11, 2018 at 06:33:45PM +0100, Ian Jackson wrote:
> > > Do you think it would be (easily) possible to have the test dir saved to
> > > the artifacts only in case of failures?
> >
> > Yes, but it wouldn't be a good idea in general. And I have a handle
> > on this bug.
>
> why wouldn't it? I believe storing extra info on failure is a sane
> thing to do in general, that has the potential to help out also in
> future failures.
If the test suite breaks completely, the results will be huge. I
think it's necessary to be much more selective.
> > I think I understand a lot more about what's going on now, after
> > reading debchange's source code. It's a bit of a mess, though.
>
> debchange's code is kind of alive, it grew in a somwhat akward
> environment :) (assuming the "mess" refers to dch!)
"mess" refers to both dch itself and my use of it in the dgit test
suite. Software, who'd have it, eh :-) ?
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#903441: dgit: autopkgtest failures in Ubuntu
On Wed, Jul 11, 2018 at 06:33:45PM +0100, Ian Jackson wrote: > > Do you think it would be (easily) possible to have the test dir saved to > > the artifacts only in case of failures? > > Yes, but it wouldn't be a good idea in general. And I have a handle > on this bug. why wouldn't it? I believe storing extra info on failure is a sane thing to do in general, that has the potential to help out also in future failures. > > Otherwise, I'd just commit the thing mentioned in the other mail (dch -D > > vs dch -r) and see whatever happens on the next regular upload. > > I think I understand a lot more about what's going on now, after > reading debchange's source code. It's a bit of a mess, though. debchange's code is kind of alive, it grew in a somwhat akward environment :) (assuming the "mess" refers to dch!) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#903441: dgit: autopkgtest failures in Ubuntu
Mattia Rizzolo writes ("Re: Bug#903441: dgit: autopkgtest failures in Ubuntu"):
> On Tue, Jul 10, 2018 at 10:57:03PM +0100, Ian Jackson wrote:
> > Can you run the test on bionic with this attached patch ?
>
> Alas, apparently the infra doesn't like it. It seems the test run just
> disappears at some point between the runner and the storage…
Huh.
> Do you think it would be (easily) possible to have the test dir saved to
> the artifacts only in case of failures?
Yes, but it wouldn't be a good idea in general. And I have a handle
on this bug.
> Otherwise, I'd just commit the thing mentioned in the other mail (dch -D
> vs dch -r) and see whatever happens on the next regular upload.
I think I understand a lot more about what's going on now, after
reading debchange's source code. It's a bit of a mess, though.
Ian.
Bug#903441: dgit: autopkgtest failures in Ubuntu
On Tue, Jul 10, 2018 at 10:57:03PM +0100, Ian Jackson wrote: > Can you run the test on bionic with this attached patch ? Alas, apparently the infra doesn't like it. It seems the test run just disappears at some point between the runner and the storage… Do you think it would be (easily) possible to have the test dir saved to the artifacts only in case of failures? Otherwise, I'd just commit the thing mentioned in the other mail (dch -D vs dch -r) and see whatever happens on the next regular upload. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#903441: dgit: autopkgtest failures in Ubuntu
Mattia Rizzolo writes ("Re: Bug#903441: dgit: autopkgtest failures in Ubuntu"):
> It just so happens that I never really read dch's manpage in full, so I
> don't remember all the options, but looking at it now, -r doesn't really
> take any option. If you need to force a distribution you need to use
> --distribution (-D). So, rolling back a bit on my previous script:
Werk. You have spotted my bug.
> > + faketime @151500 dch -r sid
So I think we have, arguably, an option parsing bug in dch, too. Here
`sid' is ignored. It is `text' (according to the FM) but that is not
meaningful with --release, which just finalises the changelog. So it
ought to have been rejected. Do you agree ?
I will send more patches later.
Thanks and sorry for being a dunce.
Ian.
Bug#903441: dgit: autopkgtest failures in Ubuntu
On Tue, Jul 10, 2018 at 10:57:03PM +0100, Ian Jackson wrote:
> Mattia Rizzolo writes ("Bug#903441: dgit: autopkgtest failures in Ubuntu"):
> > I'll wait for a debdiff to apply on top of 5.8 :)
>
> I am confused by what I think is the behaviour of dch in this test.
>
> In the test, dgit tries to upload to the suite bionic in the distro
> test-dummy. The suite is supposed to come from the changelog. The
> dch invocations were:
>
> + faketime @151500 dch -v 2.0-1 -m 'new upstream (did gbp import-orig)'
> + faketime @151500 dch -r sid
>
> The first one of these ought to make an UNRELEASED entry AFAICT (even
> reading bionic's dch). The second an entry targeting sid.
>
> I tried to repro this by copying debchange.pl from bionic's devscripts
> into my /usr/bin and running the test with DEBCHANGE_VENDOR=Ubuntu.
> But it passed.
dch in ubuntu is not any different than in debian really. IMHO the
easiest way to test for dch behaviour is to just run an ubuntu chroot…
and I believe dch is not doing what you'd expect:
root@warren:/# mkdir foo
root@warren:/# cd foo
root@warren:/foo# mkdir debian
root@warren:/foo# dch --create
-> write something sane
root@warren:/foo# faketime @151500 dch -v 2.0-1 -m 'new upstream (did gbp
import-orig)'
root@warren:/foo# cat debian/changelog
foo (2.0-1) UNRELEASED; urgency=medium
* new upstream (did gbp import-orig)
-- Mattia Rizzolo Wed, 03 Jan 2018 17:20:00 +
foo (0-1) unstable; urgency=medium
* Initial release. (Closes: #XX)
-- Mattia Rizzolo Wed, 11 Jul 2018 07:40:30 +
root@warren:/foo# faketime @151500 dch -r sid
root@warren:/foo# cat debian/changelog
foo (2.0-1) cosmic; urgency=medium
* new upstream (did gbp import-orig)
-- Mattia Rizzolo Wed, 03 Jan 2018 17:20:00 +
foo (0-1) unstable; urgency=medium
* Initial release. (Closes: #XX)
-- Mattia Rizzolo Wed, 11 Jul 2018 07:40:30 +
root@warren:/foo#
I.e. it is not 'sid' in the topmost entry.
It just so happens that I never really read dch's manpage in full, so I
don't remember all the options, but looking at it now, -r doesn't really
take any option. If you need to force a distribution you need to use
--distribution (-D). So, rolling back a bit on my previous script:
root@warren:/foo# faketime @151500 dch -v 2.0-1 -m 'new upstream (did gbp
import-orig)'
root@warren:/foo# faketime @151500 dch -D sid -r ''
libdistro-info-perl is not installed, Debian release names are not known.
libdistro-info-perl is not installed, Ubuntu release names are not known.
dch warning: Unable to determine if sid is a valid Ubuntu release.
root@warren:/foo# cat debian/changelog
foo (2.0-1) sid; urgency=medium
* new upstream (did gbp import-orig)
-- Mattia Rizzolo Wed, 03 Jan 2018 17:20:00 +
foo (0-1) unstable; urgency=medium
* Initial release. (Closes: #XX)
-- Mattia Rizzolo Wed, 03 Jan 2018 17:20:00 +
root@warren:/foo#
And there you end up with warnings due to heuristic that tries to be
helpful, at which point I'd just add --vendor as well.
> Can you run the test on bionic with this attached patch ?
>
> Note that this will cause all of the working stuff from the tests to
> turn up in AUTOPKGTEST_ARTIFACTS. If you run this in a fully formal
> way on the whole test suite, the result will be about 300Mby. If that
> is too much, run just --testname=gdr-makepatches7.
I believe 300M are fine for one-shot and test things like this.
I'm trying to run it within my own PPA to avoid uploading it to ubuntu
itself, it's my first time, I shall see how it goes.
http://autopkgtest.ubuntu.com/running#pkg-dgit
(in paricular, I'm unsure whether I'd be able to retrieve the artifacts,
the documentation doesn't say, but I have hopes I can forge the url).
> Alternatively, you can run this in an ad-hoc way out of the build
> tree. (i) dgit clone dgit (ii) apply patch (iii) install the
> test-dependencies for the gdr-makepatches7 test (which are all
> harmless to have on your system)
> (iv)
> tests/using-intree tests/tests/gdr-makepatches7 2>&1 |tee log
This doesn't seem to work:
root@warren:/dgit/dgit# tests/using-intree tests/tests/gdr-makepatches7 2>&1
|tee log
++ set -o pipefail
++ . tests/lib-core
++ . tests/lib-restricts
++ trap 'test $? = 0 || t-report-failure' EXIT
++ t-filter-out-git-hyphen-dir
++ local pathent
+++ type -p git-rev-parse
+++ :
++ pathent=
++ case "$pathent" in
++ return
++ t-set-intree
++ '[' x/dgit/dgit = x ']'
++ : /dgit/dgit/dgit
++ : /dgit/dgit/dgit-badcommit-fixup
++ : /dgit/dgit/infra/dgit-repos-server
++ : /dgit/dgit/infra/dgit-ssh-dispatch
++ : /dgit/dgit/infra/
++ : /dgit/dgit/git-debrebase
++ : /dgit/dgit
++ export DGIT_TEST DGIT_BADCOMMIT_FIXUP
++ export DGIT_REPOS_SERVER_TEST DGIT_SSH_DISPATCH_TEST
++ export DGIT_MANPAGES_SOURCE_DIR
++ export PERLLIB=/dgit/dgit
++ PERLLIB=/dgit/d
Bug#903441: dgit: autopkgtest failures in Ubuntu
Mattia Rizzolo writes ("Bug#903441: dgit: autopkgtest failures in Ubuntu"):
> I'll wait for a debdiff to apply on top of 5.8 :)
I am confused by what I think is the behaviour of dch in this test.
In the test, dgit tries to upload to the suite bionic in the distro
test-dummy. The suite is supposed to come from the changelog. The
dch invocations were:
+ faketime @151500 dch -v 2.0-1 -m 'new upstream (did gbp import-orig)'
+ faketime @151500 dch -r sid
The first one of these ought to make an UNRELEASED entry AFAICT (even
reading bionic's dch). The second an entry targeting sid.
I tried to repro this by copying debchange.pl from bionic's devscripts
into my /usr/bin and running the test with DEBCHANGE_VENDOR=Ubuntu.
But it passed.
Can you run the test on bionic with this attached patch ?
Note that this will cause all of the working stuff from the tests to
turn up in AUTOPKGTEST_ARTIFACTS. If you run this in a fully formal
way on the whole test suite, the result will be about 300Mby. If that
is too much, run just --testname=gdr-makepatches7.
Alternatively, you can run this in an ad-hoc way out of the build
tree. (i) dgit clone dgit (ii) apply patch (iii) install the
test-dependencies for the gdr-makepatches7 test (which are all
harmless to have on your system)
(iv)
tests/using-intree tests/tests/gdr-makepatches7 2>&1 |tee log
Ian.
diff --git a/tests/lib b/tests/lib
index 4ef275ca..6ee6133d 100644
--- a/tests/lib
+++ b/tests/lib
@@ -40,6 +40,10 @@ testname="${DGIT_TEST_TESTNAME-${0##*/}}"
export DGIT_TEST_TROOT=$troot
tmp=$ADTTMP
+if [ x"$AUTOPKGTEST_ARTIFACTS" != x ]; then
+ tmp=$AUTOPKGTEST_ARTIFACTS/tmp
+ mkdir -p -- "$tmp"
+fi
if [ x"$tmp" = x ]; then
export DGIT_TEST_BYHAND=1
mkdir -p tests/tmp
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#903441: dgit: autopkgtest failures in Ubuntu
Mattia Rizzolo writes ("Re: Bug#903441: dgit: autopkgtest failures in Ubuntu"):
> On Tue, Jul 10, 2018 at 11:55:57AM +0100, Ian Jackson wrote:
> > I don't think it's possible to add something to the artifacts, from
> > within a test. I didn't provide any way to do that in my original
> > spec or implementation.
>
> mh? Yes it is, just dump stuff in $AUTOPKGTEST_ARTIFACTS (defined if
> the controlling engine supports it (i.e. sadt doesn't)).
Oh! Blimey. I hadn't realised that. I also don't know how I mised
it in the doc. Sorry.
I am tempted to make my tests use AUTOPKGTEST_ARTIFACTS for their tmp,
if it is set. I will do a du to see how big the results are, but to
keep performance sane I have generally kept things small.
> > > If you wish, I can also apply a patch and try to upload it to ubuntu,
> >
> > Thanks, I will probably take you up on that.
>
> I'll wait for a debdiff to apply on top of 5.8 :)
Right, thanks.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#903441: dgit: autopkgtest failures in Ubuntu
On Tue, Jul 10, 2018 at 11:55:57AM +0100, Ian Jackson wrote:
> Mattia Rizzolo writes ("Re: Bug#903441: dgit: autopkgtest failures in
> Ubuntu"):
> > On Tue, Jul 10, 2018 at 11:12:01AM +0100, Ian Jackson wrote:
> > > Thanks. I don't have an install of cosmic and the test logs are not
> > > quite sufficient. Can I get a copy of the temporary directory after
> > > one of these test runs ?
> >
> > If you are not putting them in the artifacts, then no, it's not
> > possible.
>
> I don't think it's possible to add something to the artifacts, from
> within a test. I didn't provide any way to do that in my original
> spec or implementation.
mh? Yes it is, just dump stuff in $AUTOPKGTEST_ARTIFACTS (defined if
the controlling engine supports it (i.e. sadt doesn't)).
> I recently reread the spec and didn't find
> it. I ended up filing
>#902780 want way to publish more than one logfile
ACK on the jumpled log…
> > Indeed, `dch` under ubuntu behaves differently than on Debian. If you
> > rely on the behaviour of dch to not change amongst different vendors,
> > you should use the `--vendor` option of dch (we had several test
> > failures due to that also in the testsuite of dch itself!).
>
> I doubt that --vendor is the right answer. I should probably just
> pass -r unstable or something. Normally I do that; I think I just
> missed one.
That's another option, yes. --vendor is used only when going through
the ehuristic thing that tries to guess what you want.
> > If you wish, I can also apply a patch and try to upload it to ubuntu,
>
> Thanks, I will probably take you up on that.
I'll wait for a debdiff to apply on top of 5.8 :)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
Bug#903441: dgit: autopkgtest failures in Ubuntu
Mattia Rizzolo writes ("Re: Bug#903441: dgit: autopkgtest failures in Ubuntu"):
> On Tue, Jul 10, 2018 at 11:12:01AM +0100, Ian Jackson wrote:
> > Thanks. I don't have an install of cosmic and the test logs are not
> > quite sufficient. Can I get a copy of the temporary directory after
> > one of these test runs ?
>
> If you are not putting them in the artifacts, then no, it's not
> possible.
I don't think it's possible to add something to the artifacts, from
within a test. I didn't provide any way to do that in my original
spec or implementation. I recently reread the spec and didn't find
it. I ended up filing
#902780 want way to publish more than one logfile
> Indeed, `dch` under ubuntu behaves differently than on Debian. If you
> rely on the behaviour of dch to not change amongst different vendors,
> you should use the `--vendor` option of dch (we had several test
> failures due to that also in the testsuite of dch itself!).
I doubt that --vendor is the right answer. I should probably just
pass -r unstable or something. Normally I do that; I think I just
missed one.
> If you wish, I can also apply a patch and try to upload it to ubuntu,
Thanks, I will probably take you up on that.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#903441: dgit: autopkgtest failures in Ubuntu
On Tue, Jul 10, 2018 at 11:12:01AM +0100, Ian Jackson wrote:
> Mattia Rizzolo writes ("Bug#903441: dgit: autopkgtest failures in Ubuntu"):
> > Package: dgit
> > Version: 5.8
> ...
> > I'm filing here these totally untriaged test failures:
> > http://autopkgtest.ubuntu.com/packages/dgit
> >
> > In particular, here is the last failure for cosmic/amd64:
> > https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/d/dgit/20180708_184758_228b6@/log.gz
>
> Thanks. I don't have an install of cosmic and the test logs are not
> quite sufficient. Can I get a copy of the temporary directory after
> one of these test runs ?
If you are not putting them in the artifacts, then no, it's not
possible.
> I suspect that what is going on is that cosmic's dch is putting
> `cosmic' into the changelog. If so, depending on dch putting
> `unstable' in would be a bug in the test suite.
Indeed, `dch` under ubuntu behaves differently than on Debian. If you
rely on the behaviour of dch to not change amongst different vendors,
you should use the `--vendor` option of dch (we had several test
failures due to that also in the testsuite of dch itself!).
If you wish, I can also apply a patch and try to upload it to ubuntu, so
you avoid boring round-trips through the debian archive (which take a
full day until it gets to ubuntu and then get tested, etc). Alas I
never set up a local environment for autopkgtest. I know it's also
possible to have autopkgtest.ubuntu.com try out packages from
Launchpad's PPAs, but that also I never tried :|
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
Bug#903441: dgit: autopkgtest failures in Ubuntu
Mattia Rizzolo writes ("Bug#903441: dgit: autopkgtest failures in Ubuntu"):
> Package: dgit
> Version: 5.8
...
> I'm filing here these totally untriaged test failures:
> http://autopkgtest.ubuntu.com/packages/dgit
>
> In particular, here is the last failure for cosmic/amd64:
> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/d/dgit/20180708_184758_228b6@/log.gz
Thanks. I don't have an install of cosmic and the test logs are not
quite sufficient. Can I get a copy of the temporary directory after
one of these test runs ?
I suspect that what is going on is that cosmic's dch is putting
`cosmic' into the changelog. If so, depending on dch putting
`unstable' in would be a bug in the test suite.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#903441: dgit: autopkgtest failures in Ubuntu
Package: dgit Version: 5.8 Hi! I'm filing here these totally untriaged test failures: http://autopkgtest.ubuntu.com/packages/dgit In particular, here is the last failure for cosmic/amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/d/dgit/20180708_184758_228b6@/log.gz -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
