rubinius

Comments and changes to this ticket

• 

  Charles Comstock November 19th, 2007 @ 03:56 PM

  • → State changed from “new” to “open”

  Those specs require root to run though so it's kinda weird.

• 

  Kevin Clark November 19th, 2007 @ 04:43 PM

  Yeah, there's also the question of what uid/gid we should be switching to for cross system compat.

• 

  Eero Saynatkari November 19th, 2007 @ 05:29 PM

  • → Milestone changed from “1.0 preview” to “1.0”

  The specs should definitely be present. Since Win32 is not an issue, we can demand sudo presence or even drop to "interactive mode" of some kind. The spec should possibly be excluded from ci.

• 

  Eero Saynatkari January 20th, 2008 @ 01:51 PM

  • → Title changed from “File#chow/::chown needs specs” to “[TODO] File#chow/::chown needs specs”

  Closing, see #268.

• 

  Ryan Davis February 29th, 2008 @ 03:32 PM

  • → Milestone changed from “1.0” to “1.0 preview”
  • → Assigned user changed from “” to “Brian Ford”
  • → Title changed from “[TODO] File#chow/::chown needs specs” to “[TODO] File#chown/::chown needs specs”

  Assigning to Brian since he owns spec-land and can think about the sudo issue in general.

• 

  Brian Ford March 17th, 2008 @ 04:12 PM

  • → State changed from “open” to “resolved”

  I added an 'as_superuser' guard to MSpec for situations like these. The guard will only yield if Process.euid == 0. While I would not necessarily recommend running all specs as superuser, you could run just the specs that need it. Hopefully, we'll be able to set up a bot in a chroot jail that can run all the specs as superuser.