Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

don't check error code of diskutil eject #4978

Merged
merged 1 commit into from Jun 19, 2014

Conversation

rolandwalker
Copy link
Contributor

Instead, check the result: does the mount path still exist?
This is intended to help with unpredictable problems with the
test suite that manifest frequently on Travis.

References: #4975, #4900, #4857

nstead, determine success by directly testing the intended effect:
does the mount path still exist?

Also:
 - retry once on failure.
 - silent success if the given mount point did not exist.

These changes are intended to help with unpredictable problems with
the test suite that manifest frequently on Travis.

References: Homebrew#4975, Homebrew#4900, Homebrew#4857
rolandwalker added a commit that referenced this pull request Jun 19, 2014
don't check error code of diskutil eject
@rolandwalker rolandwalker merged commit e6cca46 into Homebrew:master Jun 19, 2014
@rolandwalker rolandwalker deleted the eject_error_code branch June 19, 2014 16:04
rolandwalker added a commit to rolandwalker/homebrew-cask that referenced this pull request Jun 25, 2014
- Raise `CaskError` instead of `Plist::ParseError` from module
- Improve error message when parse result is empty
- remove leading garbage text and emit it to stderr (seen in Homebrew#5060)
- remove trailing garbage text and emit it to stderr (seen in Homebrew#4819)

This has the incidental effect of emitting DMG licenses during
installation, which seems desirable as permanent functionality.

If not permanent, the warnings to STDERR should still be kept
temporarily to help get better bug reports on `hdiutil`.

A bug wrt DMG licenses must have been introduced in one of
Homebrew#4892, Homebrew#4887, Homebrew#4889, Homebrew#4900, Homebrew#4975, Homebrew#4978, or Homebrew#4857.  Presumably,
the cause is that STDERR was previously silenced when running
`hdiutil`.  It would be cleaner (and more reliable) to redirect
STDERR and examine it separately, rather than clean up the
merged outputs.

closes Homebrew#4819
closes Homebrew#5060
@Homebrew Homebrew locked and limited conversation to collaborators May 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant