Opened 19 years ago
Closed 16 years ago
#38 closed task (fixed)
Error codes on Windows not working
| Reported by: | cmlenz | Owned by: | cmlenz |
|---|---|---|---|
| Priority: | trivial | Milestone: | 0.4 |
| Component: | Recipe commands | Version: | |
| Keywords: | Cc: | ||
| Operating System: | Windows |
Description
The results of a spawned recipe command are interpreted using the return code (0 for success, anything else for failure). This doesn't appear to work for build slaves running on Win32.
Attachments (0)
Change History (12)
comment:1 Changed 19 years ago by cmlenz
- Milestone changed from 0.3 to 0.4
comment:2 Changed 19 years ago by cmlenz
- Priority changed from major to critical
- Status changed from new to assigned
comment:3 Changed 19 years ago by cmlenz
(Testing notification)
comment:4 Changed 19 years ago by cmlenz
(More notification testing)
comment:5 Changed 19 years ago by cmlenz
- Resolution set to fixed
- Status changed from assigned to closed
Fixed in [163].
comment:6 Changed 19 years ago by cmlenz
- Operating System set to Windows
comment:7 Changed 18 years ago by russell quinn
- Resolution fixed deleted
- Status changed from closed to reopened
hi there,
i am using the latest version of bitten, but am still having trouble getting windows application error codes working. i am running a batch file, which definitely returns a 0 to indicate a failure, but this is still marked in trac as a success.
comment:8 Changed 18 years ago by russell quinn
sorry.
it definitely returns a 1 to indicate a failure...
comment:9 Changed 18 years ago by russell@…
discovered problem and have created ticket:126 to detail a possible solution
comment:10 Changed 17 years ago by anonymous
i am using the latest version of bitten, but am still having trouble getting windows application error codes working. i am running a batch file, which definitely returns a 0 to indicate a failure, but this is still marked in trac as a success. I have changed it already! Thanks for all.
comment:11 Changed 16 years ago by iain@…
- Priority changed from critical to trivial
- Type changed from defect to task
This ticket should be closed. The original problem was fixed, and the resolution for Russell's subsequent problem (not a bitten bug) is documented in #126.
comment:12 Changed 16 years ago by dfraser
- Resolution set to fixed
- Status changed from reopened to closed
This is pretty important.