Remove "everything matched" assertions from CuDNN object-based checkpointing tests
After cl/194315742 the assertions correctly point out that there are some Python objects which aren't matched (they don't have variables). Another option would be to mark these as special/optional, which we can implement if there's a need. PiperOrigin-RevId: 194416864
Loading
Please sign in to comment