Closed Bug 20727 Opened 25 years ago Closed 25 years ago

Error handling not correct when Mac-app execution runs on non-Mac system

Categories

(Core Graveyard :: Installer: XPInstall Engine, defect, P3)

x86
Windows NT

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: depman1, Assigned: dbragg)

References

Details

Build 1999120208-M12 1. Run on NT, Linux, or Win system. 2. Go to XPInstall Test page: http://jimbob/trigger2.html 3. From the dropdown menu, select this script: a_execute_mac. Script installs and tries executing SimpleText. 4. Press Trigger case. OK. 5. Check the logfile Results: (logfile contents from NT test): http://jimbob/jars/a_execute_mac.jar -- 12/03/1999 10:49:50 --------------------------------------------------------------------------- Acceptance: a_execute_mac ------------------------- ** Execute returns: 0 Install **FAILED** with error -2142044161 Install **FAILED** with error -2142044161 Finished Installation 12/03/1999 10:49:52 Expected: Correct error handling. When running Execute API, XPInstall spawns a process to run SimpleText. It's showing in "** Execute returns: 0" that the process was spawned successfully. That's fine if all the routine should do is set the process in motion. (If it should determine whether it actually ran or not, that would be something else!). But what isn't correct is the internal handling. Getting "Install FAILED" with a garbage error number. And why did we get it twice? ******************************************************************************* Here's Jimmy's a_execute_mac script: //////////////////////////////////////////////////////////////////////////////// //////// // a_execute_mac.js // // Acceptance test // • Checks the 1 parameter form of Execute; executes SimpleText // // ~ XPInstall QA // July 23, 1999 // //////////////////////////////////////////////////////////////////////////////// //////// var vi = "1.0.1.12" Install.StartInstall("Acceptance: a_execute_mac", "acceptance", vi, 0); err = Install.Execute("SimpleText"); Install.LogComment("Execute returns: " + err); if (0 == Install.GetLastError()) Install.FinalizeInstall(); else Install.AbortInstall();
I also executed a_execute_unix script on NT. It also returns "Install FAILED" with crazy error number. Script attempts to execute DTPad.
Summary: Error handling not being handled correctly when Mac-app execution run on non-Mac system → Error handling not correctt when Mac-app execution runs on non-Mac system
Summary: Error handling not correctt when Mac-app execution runs on non-Mac system → Error handling not correct when Mac-app execution runs on non-Mac system
Target Milestone: M15
Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall Engine
reassign to dbragg bug meeting 3/20
Assignee: cathleen → dbragg
Depends on: 24984
moving to M16
Target Milestone: M15 → M16
boundary test, but okay. ------------------------------------------------------------------------------- http://jimbob/jars/a_execute_mac.jar -- 04/23/2000 22:23:09 ------------------------------------------------------------------------------- Acceptance: a_execute_mac ------------------------- ** Execute returns: 0 [1/1] Executing: /tmp//xpinstall Install completed successfully Finished Installation 04/23/2000 22:23:09 (Note the extra slash. This is another bug in the GetFolder(TEMP)....)
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Builds: 2000-04-27-09-M16(LINUX), 2000-04-27-09-M16(WIN) No more FAIL messages from install.log. Marking Verified.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.