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
The Date-dependent tests currently fail at HEAD with
FAILED sharktank/tests/models/vae/vae_test.py::VaeFluxDecoderTest::testCompareBF16EagerVsHuggingface - RuntimeError: Given groups=1, weight of size [512, 16, 3, 3], expected input[1, 1, 4096, 64] to have 16 channels, but got 1 channels instead
FAILED sharktank/tests/models/vae/vae_test.py::VaeFluxDecoderTest::testCompareF32EagerVsHuggingface - RuntimeError: Given groups=1, weight of size [512, 16, 3, 3], expected input[1, 1, 4096, 64] to have 16 channels, but got 1 channels instead
FAILED sharktank/tests/models/vae/vae_test.py::VaeFluxDecoderTest::testVaeIreeVsHuggingFace - RuntimeError: Given groups=1, weight of size [512, 16, 3, 3], expected input[1, 1, 4096, 64] to have 16 channels, but got 1 channels instead
This was first reported by @renxida who commented on #973. However, it seems that the test started when commit ab42f0c / PR #876 was landed by @KyleHerndon, see the logs. Unfortunately, the test was red before but with a different error
FAILED sharktank/tests/models/vae/vae_test.py::VaeFluxDecoderTest::testVaeIreeVsHuggingFace - RuntimeError: Error invoking function: c/runtime/src/iree/hal/drivers/hip/event_semaphore.c:677: ABORTED; the semaphore was aborted; while invoking native function hal.fence.await; while calling import;
[ 0] bytecode module.decode:84 {self._temp_dir}/flux_vae_bf16.mlir:140:3
(logs here) which seems to have been introduced with commit 9b829cd by @rsuderman but this test now fails with a different error as mentioned above.
The text was updated successfully, but these errors were encountered:
The Date-dependent tests currently fail at HEAD with
This was first reported by @renxida who commented on #973. However, it seems that the test started when commit ab42f0c / PR #876 was landed by @KyleHerndon, see the logs. Unfortunately, the test was red before but with a different error
(logs here) which seems to have been introduced with commit 9b829cd by @rsuderman but this test now fails with a different error as mentioned above.
The text was updated successfully, but these errors were encountered: