Skip to content

Caffe::set_random_seed was executed 569736 times for the CPU tests #468

@kloudkl

Description

@kloudkl

I executed build/test/test_all.testbin --gtest_filter="*CPU*" &> test.log to test #415 because I don't have access to GPU at the moment. There were 569736 log messages showing curand not available. Skipping setting the curand seed. They were caused by the multiple invocation of Caffe::set_random_seed in GradientChecker<Dtype>::CheckGradientSingle which was called by CheckGradientExhaustive in the inner loop of a two-layer for loop. Is repeatedly setting the random seed necessary?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions