Source: golang-github-viant-toolbox Version: 0.33.2-3 Hi,
While rebuilding the reverse dependencies of another package I was updating, I saw that your package failed to build in my sid sbuild environment. Specifically, there are occasional test failures that seem like they may be more easily seen on a heavily-loaded build host. From two different builds: > === RUN TestNewFileSetInfoInfo > panic: unexpected call to os.Exit(0) during test > > goroutine 56 [running]: > os.Exit(0x0) > /usr/lib/go-1.18/src/os/proc.go:68 +0x55 > github.com/viant/toolbox.(*LogStream).manageWritesInBatch(0xc000232240) > > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/viant/toolbox/file_logger.go:152 > +0x165 > github.com/viant/toolbox.(*FileLogger).NewLogStream.func1() > > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/viant/toolbox/file_logger.go:219 > +0x1d > created by github.com/viant/toolbox.(*FileLogger).NewLogStream > > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/viant/toolbox/file_logger.go:218 > +0x170 > FAIL github.com/viant/toolbox 2.994s and > === RUN TestLogger > --- PASS: TestLogger (2.46s) > panic: unexpected call to os.Exit(0) during test > > goroutine 163 [running]: > os.Exit(0x0) > /usr/lib/go-1.18/src/os/proc.go:68 +0x55 > github.com/viant/toolbox.(*LogStream).manageWritesInBatch(0xc0003220c0) > > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/viant/toolbox/file_logger.go:152 > +0x165 > github.com/viant/toolbox.(*FileLogger).NewLogStream.func1() > > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/viant/toolbox/file_logger.go:219 > +0x1d > created by github.com/viant/toolbox.(*FileLogger).NewLogStream > > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/viant/toolbox/file_logger.go:218 > +0x170 > FAIL github.com/viant/toolbox 2.781s
signature.asc
Description: This is a digitally signed message part
