graphscope复现ldbc测试query7有一半左右错误,请问原因 #3122
-
如题,使用ldbc官网的附件,生成10g数据跑正确性测试,query7一半错误,和预期结果有差距 config/validate.properties配置文件内容: printQueryNames=false status=1 ldbc.snb.interactive.update_interleave=895969 operation_count=10000 ldbc.snb.interactive.updates_dir=/test_data_10/social_network ldbc.snb.interactive.LdbcQuery1_freq=1 ldbc.snb.interactive.LdbcQuery1_enable=true ldbc.snb.interactive.LdbcShortQuery1PersonProfile_enable=true ldbc.snb.interactive.LdbcUpdate1AddPerson_enable=true |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
这个可能是闰秒的问题,我们audit使用的是v0.3.6的specification和对应的driver,最新版本的specification里IC7的定义里有一些对于闰秒的修正: Validation rule: Depending on whether the system-under-test supports leap seconds or uses UTC-SLS (UTC with Smoothed Leap Seconds), a difference of 1 minute can occur between the minutesLatency results of two correct implementations when the time interval includes June 30, 2012, when there was a leap second. Therefore, the minutesLatency value is validated using a tolerance of 1 minute. 如果照这个描述,看起来这些diff都在1分钟以内,是能够接受的(但那个版本的driver还是判错了) 能否麻烦你提供一下你的10g数据及正确结果的生成方式呢?谢谢 |
Beta Was this translation helpful? Give feedback.
这个可能是闰秒的问题,我们audit使用的是v0.3.6的specification和对应的driver,最新版本的specification里IC7的定义里有一些对于闰秒的修正:
Validation rule: Depending on whether the system-under-test supports leap seconds or uses UTC-SLS (UTC with Smoothed Leap Seconds), a difference of 1 minute can occur between the minutesLatency results of two correct implementations when the time interval includes June 30, 2012, when there was a leap second. Therefore, the minutesLatency value is validated using a tolerance of 1 minute.
如果照这个描述,看起来这些diff都在1分钟以内,是能够接受的(但那个版本的driver还是判错了)
能否麻烦你提供一下你的10g数据及正确结果的生成方式呢?谢谢
我们想尝试复现一下这些报错,针对错误日志,也可以确定是否为闰秒的问题