system HF Staff commited on
Commit
f8234dc
·
verified ·
1 Parent(s): 1b9ae8b

reports runs/2026-10-21-reduce-cigna-39617219734

Browse files
runs/2026-10-21-reduce-cigna-39617219734/reduce-14.tail.log ADDED
@@ -0,0 +1,24 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ Traceback (most recent call last):
2
+ File "/opt/hostedtoolcache/Python/3.12.15/x64/bin/ticdata", line 6, in <module>
3
+ sys.exit(main())
4
+ ^^^^^^
5
+ File "/home/runner/work/ratecommons/ratecommons/src/ticdata/cli.py", line 160, in main
6
+ res = reduce.reduce_part(a.payer, a.release, int(a.part), cfg.work_bucket, outdir, token=tok)
7
+ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8
+ File "/home/runner/work/ratecommons/ratecommons/src/ticdata/reduce.py", line 80, in reduce_part
9
+ res = reduce_part_local(local, payer, release, part, out)
10
+ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
11
+ File "/home/runner/work/ratecommons/ratecommons/src/ticdata/reduce.py", line 115, in reduce_part_local
12
+ con.execute(f"""
13
+ _duckdb.OutOfMemoryException: Out of Memory Error: failed to offload data block of size 256.0 KiB (72.4 GiB/72.4 GiB used).
14
+ This limit was set by the 'max_temp_directory_size' setting.
15
+ By default, this setting utilizes the available disk space on the drive where the 'temp_directory' is located.
16
+ You can adjust this setting, by using (for example) PRAGMA max_temp_directory_size='10GiB'
17
+
18
+ Possible solutions:
19
+ * Reducing the number of threads (SET threads=X)
20
+ * Disabling insertion-order preservation (SET preserve_insertion_order=false)
21
+ * Increasing the memory limit (SET memory_limit='...GB')
22
+
23
+ See also https://duckdb.org/docs/stable/guides/performance/how_to_tune_workloads
24
+ /dev/root 145G 64G 81G 45% /