-
Notifications
You must be signed in to change notification settings - Fork 33
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
labelblk test failure on linux #299
Comments
BTW, it isn't obvious what is causing the failure from the test log, but the log does indicate that some calls to
Just in case those missing log messages might contain the clue to the |
A fix to the comment system was committed. Maybe it's the actual logging system causing the error for some Go versions? |
I've discovered an issue with the test suite: If I run I can force the tests to run via So... in your setup, does it matter if you use |
I found the issue, kinda. I had recently re-installed Docker for Mac on my laptop, and that's when this trouble began. It turns out that the default RAM allocation for the Docker Engine is only 2 GB, and -- apparently -- that causes random errors like the one shown above. When I increased the RAM for Docker to 4 GB, everything works smoothly and I can no longer reproduce the test failure. Very strange, but oh well, at least it's fixed now! |
As mentioned over Slack, I'm seeing a weird test failure when building DVID within the
flyem-build
Docker container.The commands to download the container from scratch and reproduce the failure are as follows.
Here's the test failure output:
Click for test log
The text was updated successfully, but these errors were encountered: