You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
so it does not seem to be a big deal, but I wanted to report this, as it catched my attention, these messages are cluttering the log, and it perhaps should be investigated what is going on here and if this might indicate some deeper issue.
Environment:
Ubuntu 22.04, ARM64 Jetson Orin Dev kit
Tensorflow 2.15.0
Keras 3.0.4 / 2.15.0
The text was updated successfully, but these errors were encountered:
I see, I already suspected that it is something with the backend. I am just puzzled why the message only happens with Keras 3, but not with Keras 2. Both Keras versions log that XLA was used, but only Keras 3 shows that warning.
Triage notes: one reason might be that Keras 3 use jit compile by default, and Keras 2 doesn't (user need to explicitly enable jit), and the warning message is probably from jit/xla.
Since Keras 3, messages
"Fallback to op-by-op mode because memset node breaks graph update"
start to clutter the log output.Example code, plain vanilla MNIST network:
Output with Keras 3.0.4:
Output same code with Keras 2.15.0:
These messages also appear in some of the examples on the official Keras webpage, for example here:
https://keras.io/examples/generative/vae/
so it does not seem to be a big deal, but I wanted to report this, as it catched my attention, these messages are cluttering the log, and it perhaps should be investigated what is going on here and if this might indicate some deeper issue.
Environment:
The text was updated successfully, but these errors were encountered: