Highlighted
Absent Member.. Absent Member..
Absent Member..
309 views

Cleanup of orchidtmp on Controllers

Jump to solution
I thought the Controller machines automatically cleaned up their test runs in the Results folder once collation was completed and the test results were "in" ALM? We had a customer fill their disk space with old runs that had accumulated in the Orchidtmp\Results folder. After manual cleanup it was fine, but I thought once a run was collated, those files were removed from the LG and Controller machines?
0 Likes
1 Solution

Accepted Solutions
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Cleanup of orchidtmp on Controllers

Jump to solution

Hello Steve,

 

The test run is going to be save on the repository (ALM).

The raw result folder is the folder that it get generated after each run, you can find it on the %temp% folder, however after the collate, this get deleted..

The orchidtmp folder did not clean automatically if there is an error during the execution and before the collate, you need to delete the logs every so often. 

 

Regards,

Daniela Gómez Alvarado
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.

View solution in original post

0 Likes
2 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Cleanup of orchidtmp on Controllers

Jump to solution

Hello Steve,

 

The test run is going to be save on the repository (ALM).

The raw result folder is the folder that it get generated after each run, you can find it on the %temp% folder, however after the collate, this get deleted..

The orchidtmp folder did not clean automatically if there is an error during the execution and before the collate, you need to delete the logs every so often. 

 

Regards,

Daniela Gómez Alvarado
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.

View solution in original post

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Cleanup of orchidtmp on Controllers

Jump to solution
That's what we found as well. If you stop a test run manually and choose not to collate, or if your test run fails for any reason, those files will never be cleaned up from the Controller's test results temp directory. In our case, this particular group stopped enough failed tests choosing not to collate to the point it filled their disk and prevented valid tests from collating. Seems like a bit of a gap to me.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.