-
Notifications
You must be signed in to change notification settings - Fork 601
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
Benchmark paniced with go1.14 #208
Comments
@janisz should we do something with it? |
@Shitaibin can you give some stats about the testing box? If the runtime is out of memory I'm not inherently sure there's much we can do about that (doesn't mean we can't try). It could also be permissions, too. Does this happen on the same box, but with go1.13? |
@mxplusb same error with go1.13 in this host. It passed all benchmark in my MacBook Pro with go1.13 |
@mxplusb @cristaloleg the cause is Info from: https://golang.org/cmd/go/#hdr-Testing_flags
|
IIRC the internal default time resolution is 1s, but that shouldn't really affect |
Comparing without My host has 8G memory, does it matter? |
8G is more than enough. Looking at what you've uploaded, it's throwing the same error, but in a different location:
Before it was the @janisz what do you think? |
@Shitaibin can you share your |
The different location is because of using Using I run the benchmark using the same parameters. It always output another panic error: |
I made a group tests using
With
Does it matter? Why |
Running benchmark will running benchmarks after running tests.
|
Myabe it's related to #148 |
What is the issue you are having?
Benchmark paniced with go1.14 in centos7.
What is BigCache doing that it shouldn't?
Should not panic when allocating memory.
Minimal, Complete, and Verifiable Example
Environment:
/etc/os-release
or winver.exe):The text was updated successfully, but these errors were encountered: