Security team has provided feedback, indeed there is a patch to merge.
Let's not merge this one yet, and instead get this + the security patch
in one go.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Changed in: iniparser (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915866
Title:
build does not run tests in test/ directory
To manage notifications ab
The attachment "Error out on failing test, and improve cleanup target"
seems to be a debdiff. The ubuntu-sponsors team has been subscribed to
the bug report so that they can review and hopefully sponsor the
debdiff. If the attachment isn't a patch, please remove the "patch"
flag from the attachme
On analysis of this issue, I found that the upstream tests are being run
- it's just that failures go unnoticed due to the test runner
unconditionally returning exit code 0, pass or fail. By enhancing this
runner to return exit code 1 upon test failure, we see the test failure
log without having t
** Tags added: fr-1142
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915866
Title:
build does not run tests in test/ directory
To manage notifications about this bug go to:
https://bugs.launchpad.
** Changed in: iniparser (Ubuntu)
Assignee: (unassigned) => Dan Bungert (dbungert)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915866
Title:
build does not run tests in test/ directory
To m