You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem? 1. Run the "helloworld" pipeline from the tutorial in the documentation.
2. Look in .bpipe/logs directory
3. Look in commandlog.txt file. What is the expected output? What do you see instead? In the documentation ( https://code.google.com/p/bpipe/wiki/Logging ), it states "If you wish to see the output log for an older job you need to find its Job Id, which you can see in the command log. Then you can find the log archived in directory called '.bpipe/logs/[Job Id].log'."
An example of a commandlog.txt file is shown at that website, with these lines:
Starting pipeline at Wed Feb 01 15:22:01 EST 2012 as Job 4225
Input files: test.txt
However, my commandlog.txt file looks like this:
Starting pipeline at Mon Jul 09 17:12:01 EDT 2012
Input files: []
Stage hello
echo Hello
Stage world
echo World
There is no "as Job " in the line beginning "# Starting pipeline ..." What version of the product are you using? On what operating system? bpipe-0.9.5.3 Please provide any additional information below. Also, there is no single job id associated with this job; apparently, there are two job ids. There are two files in .bpipe/logs associated with the single job that I ran:
ls .bpipe/logs/
20038.log 20045.bpipe.log
I expected to see two files with the same id, e.g.,
20038.log, 20038.bpipe.log
Also, there is no single job id associated with this job;
apparently, there are two job ids. There are two files
in .bpipe/logs associated with the single job that I ran
Just a note that this part has been addressed in the source code and should be released in 0.9.6 - the job id will be the same for both files.
From andrew.o...@gmail.com on 2012-07-10T07:24:47Z
What steps will reproduce the problem? 1. Run the "helloworld" pipeline from the tutorial in the documentation.
2. Look in .bpipe/logs directory
3. Look in commandlog.txt file. What is the expected output? What do you see instead? In the documentation ( https://code.google.com/p/bpipe/wiki/Logging ), it states "If you wish to see the output log for an older job you need to find its Job Id, which you can see in the command log. Then you can find the log archived in directory called '.bpipe/logs/[Job Id].log'."
An example of a commandlog.txt file is shown at that website, with these lines:
Starting pipeline at Wed Feb 01 15:22:01 EST 2012 as Job 4225
Input files: test.txt
However, my commandlog.txt file looks like this:
Starting pipeline at Mon Jul 09 17:12:01 EDT 2012
Input files: []
Stage hello
echo Hello
Stage world
echo World
There is no "as Job " in the line beginning "# Starting pipeline ..." What version of the product are you using? On what operating system? bpipe-0.9.5.3 Please provide any additional information below. Also, there is no single job id associated with this job; apparently, there are two job ids. There are two files in .bpipe/logs associated with the single job that I ran:
ls .bpipe/logs/
20038.log 20045.bpipe.log
I expected to see two files with the same id, e.g.,
20038.log, 20038.bpipe.log
Attachment: 20045.bpipe.log 20038.log commandlog.txt
Original issue: http://code.google.com/p/bpipe/issues/detail?id=41
The text was updated successfully, but these errors were encountered: