-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SystemError: flush: Bad file descriptor on Travis but not on local machine #39
Comments
Hi, Thanks for reporting. I haven't run across this, and I don't know what the problem is off hand. I'll try to take a look, but not sure how soon. If you discover anything about it, please post back! Link with an example from LoggedDicts.jl: https://travis-ci.org/JockLawrie/LoggedDicts.jl/jobs/120814199#L160-L168. |
Okay, a small hint: the only |
The curious thing is that each call to set!, pop!, push! and delete! calls info(), which then writes to the log file. This all goes without a hitch until the end of runtests.jl. That is, the error is raised only when info() is called for the 9th time. The only thing I can think of is that the log file is closed by some Travis setting...but then surely the test suite from Logging.jl would have encountered this problem. So I'm stumped. |
New fact: Commenting out writes (not logs) to other files passes on Linux On 6 April 2016 at 13:18, Kevin Squire [email protected] wrote:
|
Now passing on OSX - no issue, it just stopped so I restarted it. So the problem seems related to writing to a stream not using Logging.jl On 6 April 2016 at 14:53, Jock Lawrie [email protected] wrote:
|
Hi there,
I am running the tests for LoggedDicts.jl, which uses Logging.jl as a dependency. On my local machine everything works well, but on Travis I consistently get the error: SystemError: flush: Bad file descriptor
Oddly, the error occurs on a line that is called several times without issue earlier in the test suite. The failure consistently occurs at the same call site (line 44 of test/runtests.jl).
It is unclear if this is a Logging.jl issue, a Travis issue or something that I'm doing wrong.
Have you seen this problem before?
Regards,
Jock
The text was updated successfully, but these errors were encountered: