Open DoctorSlimm opened 1 year ago
See related #10038
And how can I make it work without throwing
Error in cpuinfo: failed to parse both lists of possible and present processors
terminate called after throwing an instance of 'onnxruntime::OnnxRuntimeException'
what(): /onnxruntime_src/include/onnxruntime/core/common/logging/logging.h:294 static const onnxruntime::logging::Logger& onnxruntime::logging::LoggingManager::DefaultLogger() Attempt to use DefaultLogger but none has been registered.
@DoctorSlimm, could you try the binary mentioned in https://github.com/microsoft/onnxruntime/issues/10038#issuecomment-1526156977? It is important to let us know whether it could fix the issue or bring new issue.
@tianleiwu Hello, I have tried your solution and recieved the same error actually. I have also posted for you my source code for information and build commands etc - I think this issue could be down to the fact that I am building the image on a mac? do you think so? Should I try to build it in inside AWS CodeBuild in an aarch64 VM instead?
https://github.com/microsoft/onnxruntime/issues/10038#issuecomment-1528154009
@DoctorSlimm, It seems that env is not initialized properly. I am not sure about root cause. If you are able to ssh to your VM, you can manually setup a python environment (with minimal packages) and test session creation with any onnx model.
@DoctorSlimm
I have tried your solution and recieved the same error actually.
I don't quite understand how that is possible if you were using the custom build, as the change in that build would only attempt to use the default logger if it existed.
i.e. this check
static bool HasDefaultLogger() { return nullptr != s_default_logger_; }
is made first, but the error comes from the attempt to use the default logger
inline const Logger& LoggingManager::DefaultLogger() {
if (s_default_logger_ == nullptr) {
// fail early for attempted misuse. don't use logging macros as we have no logger.
ORT_THROW("Attempt to use DefaultLogger but none has been registered.");
}
For that to happen s_defaultlogger, a static member in the LoggingManager, would have to be null and not null at essentially the same time.
I don't believe that's possible, which would suggest your setup was not using the custom onnxruntime python package if the error is coming from the cpuinfo init.
Of course it could be a completely unrelated place that is attempting to use the default logger. We could setup a different custom build to test if that is the case.
@DoctorSlimm,
RUN bash save_model.sh instructor "hkunlp/instructor-base"
Were you able to successfully convert Instructor model to onnx format?
Describe the issue
To reproduce
Urgency
urgent, piloting to early customers this week and have been up for 2 days
Platform
Linux
OS Version
AWS Lambda, Image built on MacOS
ONNX Runtime Installation
Released Package
ONNX Runtime Version or Commit ID
not sure
ONNX Runtime API
Python
Architecture
ARM64
Execution Provider
Other / Unknown
Execution Provider Library Version
(CPU Only... ARM64 I think?)