I'm also getting random "memleak" errors that probably aren't. We are mostly interested in linear memory growth with multiple calls (i.e. malloc without free), not overall constants (like a new ring was used and the parent is now cached somewhere). The memory leak tests should probably do multiple tries and only fail if ram usage consistently grows.
On Saturday, June 12, 2021 at 9:28:31 PM UTC+2 [email protected] wrote: > > > > On Jun 6, 2021, at 11:40, Volker Braun <[email protected]> wrote: > > > > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html > > Built without problems from a fresh clone of the develop tree on macOS > 10.15.7 (2019 MBP, 8-core Core i9). > > Testing (‘ptestlong’) yielded one failures: > > sage -t --long --warn-long 78.7 --random-seed=0 > src/sage/graphs/bipartite_graph.py > > The failure is the same as I reported earlier, for another system: > File "src/sage/graphs/bipartite_graph.py", line 329, in > sage.graphs.bipartite_graph.BipartiteGraph.__init__ > Failed example: > print(round(get_memory_usage() - start_mem)) > Expected: > 0.0 > Got: > 3.0 > > Again, the failures were more or less the same, with varying non-0.0 > values appearing about 20-30% of the time, when I ran the test in a loop. > > Justin > > > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/ee98a8e1-fb4e-4406-b30c-573204921f1fn%40googlegroups.com.
