On Mon, Aug 13, 2018 at 6:12 AM, Johannes Schauer wrote:
> The third commit adds this. It adds a new scenario type called "cross" which
> will run dose-builddebcheck with the build architecture amd64 and all the host
> architectures that the software is otherwise testing. Theoretically, we could
Hi,
I now have code that fixes the issues raised in this bug. It certainly still
has some rough edges but the functionality is implemented. You can find the
code in my top commits to this repository:
https://salsa.debian.org/josch/dose
Amongst the nine top commits, six fix some drive-by issues.
Hi,
Did something happen at DebConf about this bug?
On the UDD side, I would be fine with importing results as long as they
are exported in a sane format (JSON, YAML, CSV, etc). I could then add
them to DMD.
Lucas
Hi,
Quoting Raphael Hertzog (2015-07-17 14:36:43)
On Fri, 17 Jul 2015, Johannes Schauer wrote:
I think for the tracker we would want a custom format, in case the
dose3 raw data format/schema changes.
right. I think that makes sense.
I don't see how it makes sense.
sadly I'll not
Hi,
On Fri, 17 Jul 2015, Ralf Treinen wrote:
The only alternative would be to invent a generic data source format
that would be useful for all possible action items that we want
to import. But a generic format for a specialized use case seems overkill.
can we defer this discussion to
On Fri, 17 Jul 2015, Johannes Schauer wrote:
I think for the tracker we would want a custom format, in case the
dose3 raw data format/schema changes.
right. I think that makes sense.
I don't see how it makes sense. If that output contains the suitable
information, let's use it and define
On Fri, Jul 17, 2015 at 1:32 PM, Johannes Schauer wrote:
Correct. My motivation to add this was something I forgot to mention in my
initial report, but this is just an implementation detail: dose3 outputs its
results in yaml format. Implementation wise, it would be easiest if
qa.d.o/dose
Hi,
Quoting Paul Wise (2015-07-17 09:42:19)
On Fri, Jul 17, 2015 at 1:32 PM, Johannes Schauer wrote:
Correct. My motivation to add this was something I forgot to mention in my
initial report, but this is just an implementation detail: dose3 outputs
its results in yaml format.
Hi,
On Fri, Jul 17, 2015 at 02:36:43PM +0200, Raphael Hertzog wrote:
On Fri, 17 Jul 2015, Johannes Schauer wrote:
I think for the tracker we would want a custom format, in case the
dose3 raw data format/schema changes.
right. I think that makes sense.
I don't see how it makes
Hi,
On Fri, Jul 17, 2015 at 12:06:23PM +0800, Paul Wise wrote:
On Thu, Jul 16, 2015 at 6:38 PM, Johannes Schauer wrote:
it would be useful to show information about unsatisfiability of binary
and source packages in DMD and the tracker. For that, qa.d.o/dose should
export machine readable
Package: qa.debian.org
Severity: wishlist
Hi,
it would be useful to show information about unsatisfiability of binary
and source packages in DMD and the tracker. For that, qa.d.o/dose should
export machine readable data of the latest runs of distcheck and
buildcheck. I guess that the dose yaml
On Thu, Jul 16, 2015 at 6:38 PM, Johannes Schauer wrote:
it would be useful to show information about unsatisfiability of binary
and source packages in DMD and the tracker. For that, qa.d.o/dose should
export machine readable data of the latest runs of distcheck and
buildcheck. I guess that
Hi,
Quoting Paul Wise (2015-07-17 06:06:23)
it would be useful to show information about unsatisfiability of binary
and source packages in DMD and the tracker. For that, qa.d.o/dose should
export machine readable data of the latest runs of distcheck and
buildcheck. I guess that the dose
13 matches
Mail list logo
