hep
hep copied to clipboard
go-hep
xrootd: possible timeout in xrdfuse or xrdproto tests
lately, there has been a string of timeouts while running travis tests. latest one:
https://travis-ci.org/go-hep/hep/jobs/408527786
ok go-hep.org/x/hep/sio 1.073s coverage: 66.9% of statements
? go-hep.org/x/hep/sio/cmd/sio-ls-records [no test files]
ok go-hep.org/x/hep/slha 1.132s coverage: 78.1% of statements
? go-hep.org/x/hep/slha/example/go-slha-basic [no test files]
ok go-hep.org/x/hep/xrootd 1.009s coverage: 0.0% of statements [no tests to run]
ok go-hep.org/x/hep/xrootd/client 28.466s coverage: 69.8% of statements
? go-hep.org/x/hep/xrootd/cmd/xrd-client [no test files]
? go-hep.org/x/hep/xrootd/cmd/xrd-cp [no test files]
? go-hep.org/x/hep/xrootd/cmd/xrd-fuse [no test files]
? go-hep.org/x/hep/xrootd/cmd/xrd-ls [no test files]
ok go-hep.org/x/hep/xrootd/cmd/xrd-srv 1.319s coverage: 30.6% of statements
ok go-hep.org/x/hep/xrootd/internal/mux 1.941s coverage: 80.3% of statements
? go-hep.org/x/hep/xrootd/internal/xrdenc [no test files]
ok go-hep.org/x/hep/xrootd/server 1.016s coverage: 74.1% of statements
? go-hep.org/x/hep/xrootd/xrdfs [no test files]
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
The build has been terminated
the 2 packages remaining to be tested are xrootd/xrdfuse and xrootd/xrdproto.
@EgorMatirov could you have a look at this?
As for now, I was able to get such stacktrace, however, I still don't really understand what happens.
this may be an issue with hanwen/go-fuse.
perhaps time to pick their brain about that?
(but I suspect they'll want a smaller reproducer...)
(but I suspect they'll want a smaller reproducer...)
The problem is that I still wasn't able to reproduce it locally. I'll try more, though.
did you try with code-coverage enabled? it does modify the code being compiled so... some "chance" to interact badly with concurrency.