On Wed, 2020-03-11 at 05:25 +, Dan Kortschak wrote:
> On Tue, 2020-03-10 at 22:07 -0700, Ian Lance Taylor wrote:
> > On Tue, Mar 10, 2020 at 3:25 AM Dan Kortschak
> > wrote:
> > >
> > > I have a package that is dependent on bazil.org/fuse for testing
> > > via a
> > > sysfs simulation package
On Tue, 2020-03-10 at 22:07 -0700, Ian Lance Taylor wrote:
> On Tue, Mar 10, 2020 at 3:25 AM Dan Kortschak
> wrote:
> >
> > I have a package that is dependent on bazil.org/fuse for testing
> > via a
> > sysfs simulation package github.com/ev3go/sisyphus.
> >
> > For historical reasons, the travi
On Tue, Mar 10, 2020 at 3:25 AM Dan Kortschak wrote:
>
> I have a package that is dependent on bazil.org/fuse for testing via a
> sysfs simulation package github.com/ev3go/sisyphus.
>
> For historical reasons, the travis testing used the -a flag (since
> removed because of the issue described here
I don’t know the -a flag and go help testflags doesn’t mention it.
I guess you turned off something in your tests
LK
On Tue, 10 Mar 2020 at 11:24, Dan Kortschak wrote:
> I have a package that is dependent on bazil.org/fuse for testing via a
> sysfs simulation package github.com/ev3go/sisyphus.
I have a package that is dependent on bazil.org/fuse for testing via a
sysfs simulation package github.com/ev3go/sisyphus.
For historical reasons, the travis testing used the -a flag (since
removed because of the issue described here).
Since Go1.14, the standard runtime tests on travis passed, bu
