[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947582#comment-13947582
 ] 

Santhosh Kumar Edukulla commented on CLOUDSTACK-5498:
-----------------------------------------------------

This has been resolved.

1. We added a new jenkins job uploading all logs to a particular share, where 
all logs are available by test suite name.

2. As well, changes in topic branch are done to facilitate this.

Iam removing this from blocker tag, in case if still finds issue, then we can 
look for 4.4

Thanks!
Santhosh

> [Atomation] Marvin - Logs are not storing to folder with suite name
> -------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5498
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5498
>             Project: CloudStack
>          Issue Type: Test
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Automation, marvin
>    Affects Versions: 4.3.0
>         Environment: Automation
>            Reporter: Rayees Namathponnan
>            Assignee: Santhosh Kumar Edukulla
>            Priority: Blocker
>             Fix For: 4.3.0
>
>
> Configure .cfg file with below data and run automation eg "test_ssvm"
>     },
>     "logger":
>         {
>           "LogFolderPath": "/Repo_30X/ipcl/cloudstack/test/logs/"
>         },
>     "globalConfig": [
>         {
>             "name": "network.gc.wait",
>             "value": "60"
>         },
>         {
>             "
> Expected result 
> Folder "test_ssvm_+timestamp" should be created under 
> /Repo_30X/ipcl/cloudstack/test/logs/", and   below 3 files should be under 
> that 
> failed_plus_exceptions.txt
> results.txt
> runinfo.txt
> Actual Result 
> Folder "timestamp" created instead of "test_ssvm_+timestamp", and i can see 
> other 3 text files; 
> Its very hard to find corresponding folder for test_ssvm, with current 
> implementation 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to