Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

cgroup related tests fail

Open
#278 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
linux, ruby

Research direction

Start by running the cgroup examples in spec/mixlib/shellout_spec.rb, especially the cases around lines 1599 and 1609, and inspect their failure output. Trace why running_cgroup is empty on Linux for both existing and newly created cgroups. Done means both reported examples pass across the affected Linux environments.

Written by the indexing model from the issue text.

Description

Status: Untriaged Type: Bug

Version:

main / latest

Environment:

Linux - tried on various distros.

  when running on a cgroup
    when cgroup exists
      should run the process under that cgroup (FAILED - 1)
    when cgroup does not exist
      should create the cgroup and run the process under it (FAILED - 2)

Failures:

  1) Mixlib::ShellOut when running on a cgroup when cgroup exists should run the process under that cgroup
     Failure/Error: expect(running_cgroup).to eql(cgroup.to_s)
     
       expected: "/user.slice/user-1000.slice/session-2.scope"
            got: ""
     
       (compared using eql?)
     # ./spec/mixlib/shellout_spec.rb:1599:in `block (4 levels) in <top (required)>'

  2) Mixlib::ShellOut when running on a cgroup when cgroup does not exist should create the cgroup and run the process under it
     Failure/Error: expect(running_cgroup).to eql(cgroup.to_s)
     
       expected: "/user.slice/user-1000.slice/test"
            got: ""
     
       (compared using eql?)
     # ./spec/mixlib/shellout_spec.rb:1609:in `block (4 levels) in <top (required)>'
Dominant language
Ruby
Stars
133
Forks
73
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from chef/mixlib-shellout

All issues in chef/mixlib-shellout

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.