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
crest-team@cutter:~/working_copies/cnf-misc-ezyang/paper/data$ ./fetch_data.sh inttpointtree-mem
+ mkdir -p ./downloaded/
+ for bench in '$BENCHES'
+ go inttpointtree-mem
+ bench=inttpointtree-mem
+ QUERY='SELECT PROGNAME,VARIANT,DATETIME,ARGS,THREADS,MINTIME,MEDIANTIME,MEDIANTIME_PRODUCTIVITY,MAXTIME,GIT_DEPTH FROM FT WHERE MEDIANTIME > 0 and PROGNAME LIKE '\''inttpointtree-mem%'\'' '
+ QUERY+='and HOSTNAME LIKE '\''%cutter%'\'''
+ QUERY+='and GIT_DEPTH >= 0'
+ hsbencher-fusion-fetch --id=905767673358.apps.googleusercontent.com --secret=REDACTED --table=CompactNF2 '--query=SELECT PROGNAME,VARIANT,DATETIME,ARGS,THREADS,MINTIME,MEDIANTIME,MEDIANTIME_PRODUCTIVITY,MAXTIME,GIT_DEPTH FROM FT WHERE MEDIANTIME > 0 and PROGNAME LIKE '\''inttpointtree-mem%'\'' and HOSTNAME LIKE '\''%cutter%'\''and GIT_DEPTH >= 0' --raw
[HSBencher.Internal.Fusion] Initializing
[HSBencher.Internal.Fusion] Fetching information from Google
[HSBencher.Internal.Fusion] REDACTED
["PROGNAME","VARIANT","ARGS","HOSTNAME","MINTIME","MEDIANTIME","MAXTIME","THREADS","RETRIES","RUNID","CI_BUILD_ID","DATETIME","MINTIME_PRODUCTIVITY","MEDIANTIME_PRODUCTIVITY","MAXTIME_PRODUCTIVITY","ALLTIMES","TRIALS","COMPILER","COMPILE_FLAGS","RUNTIME_FLAGS","ENV_VARS","BENCH_VERSION","BENCH_FILE","UNAME","PROCESSOR","TOPOLOGY","GIT_BRANCH","GIT_HASH","GIT_DEPTH","WHO","ETC_ISSUE","LSPCI","FULL_LOG","MEDIANTIME_ALLOCRATE","MEDIANTIME_MEMFOOTPRINT","ALLJITTIMES","BYTES_ALLOC","BYTES_COPIED","CPUTIME","CYCLES","NUMGC","BYTES","BYTES_SENT","COMM","DESERIALIZE","GENTREE","SIZE","TOTALTIME","BYTES_ALLOCATED"]
hsbencher-fusion-fetch: getData: failed to parse JSON response:
valFromObj: Could not find key: "rows"
That failed to parse JSON response is an unfriendly message meaning the real thing which is, "No results!"
The text was updated successfully, but these errors were encountered:
That failed to parse JSON response is an unfriendly message meaning the real thing which is, "No results!"
The text was updated successfully, but these errors were encountered: