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
Multipack requires runing through the dataset and computing some statistics at the beginning at every epoch. It was reported by @anhuong that when setting the loglevel in DEBUG that we observe some TypingErrors during the JIT compilation
It is unclear if there is a severe effect, since the function still executes correctly. It could be that it internally fallsback to the non-compiled version. But regardless this is a numba JIT error
Traceback (most recent call last):
File "/workspace/fms/run-benches/lib/python3.10/site-packages/numba/core/typeinfer.py", line 160, in propagate
constraint(typeinfer)
File "/workspace/fms/run-benches/lib/python3.10/site-packages/numba/core/typeinfer.py", line 581, in __call__
fnty = typevars[self.func].getone()
File "/workspace/fms/run-benches/lib/python3.10/site-packages/numba/core/typeinfer.py", line 128, in getone
raise TypingError("Undecided type {}".format(self))
numba.core.errors.TypingError: Undecided type $152load_method.20 := <undecided>
During: resolving caller type: $152load_method.20
During: typing of call at /workspace/fms-acceleration/plugins/attention-and-distributed-packing/src/fms_acceleration_aadp/multipack_sampler.py (331)
Traceback (most recent call last):
File "/workspace/fms/run-benches/lib/python3.10/site-packages/numba/core/typeinfer.py", line 160, in propagate
constraint(typeinfer)
File "/workspace/fms/run-benches/lib/python3.10/site-packages/numba/core/typeinfer.py", line 581, in __call__
fnty = typevars[self.func].getone()
File "/workspace/fms/run-benches/lib/python3.10/site-packages/numba/core/typeinfer.py", line 128, in getone
raise TypingError("Undecided type {}".format(self))
numba.core.errors.TypingError: Undecided type $108load_method.12 := <undecided>
During: resolving caller type: $108load_method.12
During: typing of call at /workspace/fms-acceleration/plugins/attention-and-distributed-packing/src/fms_acceleration_aadp/multipack_sampler.py (299)
Traceback (most recent call last):
File "/workspace/fms/run-benches/lib/python3.10/site-packages/numba/core/typeinfer.py", line 160, in propagate
constraint(typeinfer)
File "/workspace/fms/run-benches/lib/python3.10/site-packages/numba/core/typeinfer.py", line 581, in __call__
fnty = typevars[self.func].getone()
File "/workspace/fms/run-benches/lib/python3.10/site-packages/numba/core/typeinfer.py", line 128, in getone
raise TypingError("Undecided type {}".format(self))
numba.core.errors.TypingError: Undecided type $108load_method.12 := <undecided>
During: resolving caller type: $108load_method.12
Multipack requires runing through the dataset and computing some statistics at the beginning at every epoch. It was reported by @anhuong that when setting the loglevel in DEBUG that we observe some
TypingErrors
during the JIT compilationIt is unclear if there is a severe effect, since the function still executes correctly. It could be that it internally fallsback to the non-compiled version. But regardless this is a numba JIT error
The
TypingError
happens in a few placeslog.txt
The text was updated successfully, but these errors were encountered: