See attached image.
Hi Geert
I have not been able to reproduce this here so far. Are you able to send us a the log file (just called log - no extension) fro the buillds server workspace. That might help us narrow down the cause, if the data is in the log file then it’s a reading problem, if not it’s a writing problem.
Also, can you take a look at the text log file (download as text), does that have the missing stage? We changed how that file was generated recently so that it is generated during the build rather than on demand. It may or may not be affected by the same issue… at least it might help steer us in the right direction.
I already checked out the log when I reported this issue. It ends like this:
[code]11:39:31 PM 1/1 test(s) Passed11:39:31 PM 11:39:31 PM Summary11:39:31 PM -------11:39:31 PM Test Run Completed.11:39:31 PM Passed 111:39:31 PM ---------11:39:31 PM Total 111:39:31 PM Results file: C:\CI_WS\Ws\210\MSTestOutput_130314119712669409.trx11:39:31 PM Test Settings: Default Test Settings11:39:31 PM 11:39:31 PM 11:39:31 PM MSTest Results: Fixtures: 1 Tests: 0 Passes: 1 Failures: 0 Errors: 0 Inconclusive: 0 Ignored: 0 Skipped: 0 Invalid: 0 11:39:33 PM Agent To Server Workspace Sync11:39:33 PM Started syncing files from the agent to the server.11:39:33 PM Finished syncing files from the agent to the server.11:39:35 PM Artifacts Registration11:39:35 PM Started registering artifacts11:39:35 PM Finished registering artifacts[/code]
The failed stage is not even listed in the log.
I think I found something interesting. It looks like it stops writing logs after the unit tests. This is a completely different project, look what happens:
https://dl.dropboxusercontent.com/u/8455721/Posts/continua_ci_stage_not_in_log_unittests.png
Hi Geert
Thanks for the info, we were able to reproduce and fix the issue, we’ll have a new build out later today.
Hi Geert
A build with the fix is available on the downloads page.
Thanks, the new release works great.