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
[ 283s] [ OK ] datareposrc.readTensors (8 ms)
[ 283s] [ RUN ] datareposrc.readFlexibleTensors
[ 286s] [ OK ] datareposrc.readFlexibleTensors (2939 ms)
[ 286s] [ RUN ] datareposrc.fps30ReadFlexibleTensors
[ 287s] Elapsed time: 0.320374 second
[ 287s] ../tests/nnstreamer_datarepo/unittest_datareposrc.cc:686: Failure
[ 287s] Expected: (0.8) < (elapsed_time), actual: 0.8 vs 0.320374
[ 287s] Elapsed time: 0.000820 second
[ 288s] Elapsed time: 1.001003 second
[ 288s] [ FAILED ] datareposrc.fps30ReadFlexibleTensors (1671 ms)
[ 288s] [ RUN ] datareposrc.readSparseTensors
@songgot, please address this issue without removing the test case.
There can be an error in datareposrc's data-generating logic that breaks the timing requirement from the .json file.
We have this issue even with documentation updates:
[238/239] Compiling C++ object 'tests/nnstreamer_datarepo/8107b62@@unittest_datareposrc@exe/gtest-all.cc.o'.
[239/239] Linking target tests/nnstreamer_datarepo/unittest_datareposrc.
1/17 unittest_common OK 0.48 s
2/17 unittest_sink OK 32.16 s
3/17 unittest_tensor_region OK 1.08 s
4/17 unittest_plugins OK 17.19 s
5/17 unittest_if OK 4.94 s
6/17 unittest_rate OK 0.37 s
7/17 unittest_latency OK 13.07 s
8/17 unittest_filter_single OK 0.01 s
9/17 unittest_join OK 0.67 s
10/17 unittest_src_iio OK 30.64 s
11/17 unittest_filter_custom OK 2.58 s
12/17 unittest_tizen_custom OK 0.01 s
13/17 unittest_tizen_custom-set OK 0.01 s
14/17 unittest_cppfilter OK 0.52 s
15/17 unittest_datareposink OK 2.22 s
16/17 unittest_datareposrc FAIL 10.16 s (exit status 1)
17/17 unittest_trainer OK 0.04 s
The text was updated successfully, but these errors were encountered:
We still have the following occasional error:
@songgot, please address this issue without removing the test case.
There can be an error in datareposrc's data-generating logic that breaks the timing requirement from the .json file.
We have this issue even with documentation updates:
The text was updated successfully, but these errors were encountered: