Can someone please elaborate on how I can control the abi tests directly?Where
exactly can I access these and refine them on a per-package basis?
How to fix the tests?
The tests are all in your hand, you can fix the dist.depcheck and dist.abicheck
by adjusting the update or the build and you can fix the package level testing
since the tests are stored in the dist-git repository of the package itself.
You have the control on the tests.
On Tuesday, January 23, 2018 2:16 PM, Matthew Miller
<mat...@fedoraproject.org> wrote:
On Tue, Jan 23, 2018 at 12:25:56PM -0600, Rex Dieter wrote:
> > There are three tests that must pass in order for updates to go to stable:
> > 0. dist.depcheck - to make sure the update's dependencies are available.
> > 1. dist.abicheck - to make sure the update's ABI remains stable in a
> > given Fedora release.
> ...
> > Finally, if it turns out you need to push an update through despite of the
> > test results, you can do so using waiver-cli (dnf install waiverdb-cli).
> > We are working on integrating this into Bodhi itself, making this easier.
> I think it unwise to make item 1 a mandatory item at this point. I'd argue
> a large number of packages do not provide public api/abi that's worth
> worrying about in this regard.
I think we should definine a set of packages where we care about this,
and enable it on a case-by-case basis and make it advisory otherwise.
--
Matthew Miller
<mat...@fedoraproject.org>
Fedora Project Leader
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
