Profuse apologies for the long delay on addressing this. To fix the
autopkgtests by disabling the proxy (thanks for the information above!),
I have created a new SRU bug report [1] for oracular and noble, and an
MP [2] for oracular.
I am unsure if I must create the noble MP right now or wait for
** Merge proposal unlinked:
https://code.launchpad.net/~pushkarnk/ubuntu/+source/puppetdb/+git/puppetdb/+merge/475170
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072516
Title:
autopkgtests fa
** Merge proposal linked:
https://code.launchpad.net/~pushkarnk/ubuntu/+source/puppetdb/+git/puppetdb/+merge/475170
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072516
Title:
autopkgtests fail
I'm flipping this to verification-failed, as the autopkgtests did *not* pass -
https://autopkgtest.ubuntu.com/packages/puppetdb/noble/amd64 and particularly
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/p/puppetdb/20240731_094926_bb178@/log.gz
It *does* look like an problem
** Tags removed: verification-done verification-done-noble
** Tags added: verification-failed verification-failed-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072516
Title:
autopkgtests fail
Could it be the squid.internal proxy, set for dep8 runs in the
infrastructure? Can you perhaps unset the proxy variables in the test,
or use noproxy (or NOPROXY) for the domains the test is trying to fetch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I can't reproduce these 403 errors locally. I wonder if failures in [1]
are due to an infra issue. I'll take a detailed look later in my day
tomorrow to attempt an explanation.
Locally, I ran:
=
$ autopkgtest puppetdb --apt-pocket=proposed=src:puppetdb -U -- lxd
autopkgtest/ubuntu/noble/amd6
According to [1], puppetdb 7.12.1-3ubuntu0.1 in noble-proposed is still
failing[2]:
729s autopkgtest [09:47:09]: summary
729s standalone PASS
729s with-puppetserverFAIL non-zero exit status 1
The only reason it's not marked as a regression in the excuses report[
TEST CASE:
1. Install and upgrade test.
- try installing and removing puppetdb 7.12.1-3ubuntu0.1
- apt install puppetdb=7.12.1-3ubuntu0.1
- try upgrading puppetdb from 7.12.1-3 to 7.12.1-3ubuntu0.1 from
noble-proposed
- apt upgrade puppetdb=7.12.1-3ubuntu0.1
2. Run autopkgtests
Hello Pushkar, or anyone else affected,
Accepted puppetdb into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/puppetdb/7.12.1-3ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Unsubscribing ubuntu-sponsors for now; see comments on LP: #2069384
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072516
Title:
autopkgtests fail on oracular & noble
To manage notifications about
This bug was fixed in the package puppetdb - 8.4.1-1ubuntu1
---
puppetdb (8.4.1-1ubuntu1) oracular; urgency=medium
* Fix autopkgtest failures (LP: #2072516)
- d/t/control: add allow-stderr to accommodate
a Java version warning
- d/t/with-puppetserver: avoid a parsing e
** Description changed:
- Currently, both tests under debian/test fail on oracular [1].
+ [ Impact ]
+ * The puppetdb autopkgtests fail on noble after the FTBFS bug [1] is fixed.
+
+ [ Test Plan ]
+ * Running autopkgtests on noble reveals the failure.
+
+ [ Where problems could occur ]
+ Curren
13 matches
Mail list logo
