It would be helpful to see how anaconda is using memory over time. --- tests/gui/outside/template.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/gui/outside/template.py b/tests/gui/outside/template.py index 9ef47b3..538cae6 100644 --- a/tests/gui/outside/template.py +++ b/tests/gui/outside/template.py @@ -60,7 +60,7 @@ if __name__ == "__main__":
f.close()
- for log in glob.glob("/tmp/*.log"): + for log in glob.glob("/tmp/*.log") + ["/tmp/memory.dat"]: shutil.copy(log, "/mnt/anactest/result/anaconda/")
# anaconda writes out traceback files with restricted permissions, so
On 10/17/2014 02:17 PM, Chris Lumens wrote:
It would be helpful to see how anaconda is using memory over time.
tests/gui/outside/template.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/gui/outside/template.py b/tests/gui/outside/template.py index 9ef47b3..538cae6 100644 --- a/tests/gui/outside/template.py +++ b/tests/gui/outside/template.py @@ -60,7 +60,7 @@ if __name__ == "__main__":
f.close()
for log in glob.glob("/tmp/*.log"):
for log in glob.glob("/tmp/*.log") + ["/tmp/memory.dat"]: shutil.copy(log, "/mnt/anactest/result/anaconda/") # anaconda writes out traceback files with restricted permissions, so
Will memory.dat always exist? Or should this script go ahead and fail if it doesn't exist?
Will memory.dat always exist? Or should this script go ahead and fail if it doesn't exist?
It should always exist, yes.
If it doesn't... hmm. That does seem like a reason for failing the test case, but perhaps I should do so in a more orderly fashion. I'll wrap some code in some more code.
- Chris
anaconda-patches@lists.fedorahosted.org