We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
panic: internal error: reaper must be started goroutine 275 [running]: github.com/canonical/pebble/internal/reaper.WaitCommand(0xc000292b00, 0xc000044708, 0x7f2824, 0xb8c1e8) /home/runner/work/pebble/pebble/internal/reaper/reaper.go:192 +0x794 github.com/canonical/pebble/internal/overlord/servstate.(*serviceData).startInternal.func2(0xc000292b00, 0xc000353a10, 0x5, 0xc0000830e0, 0xc0000ddb80) /home/runner/work/pebble/pebble/internal/overlord/servstate/handlers.go:414 +0x51 created by github.com/canonical/pebble/internal/overlord/servstate.(*serviceData).startInternal /home/runner/work/pebble/pebble/internal/overlord/servstate/handlers.go:413 +0x111e FAIL github.com/canonical/pebble/internal/overlord/servstate 2.850s
See the full test logs here.
I can't quite tell from the logs which test is failing.
The text was updated successfully, but these errors were encountered:
Still observing this here.
Sorry, something went wrong.
@barrettj12 Hi Jordan, yes, I will tackle servstate next ...
#266 Should now fix this.
Successfully merging a pull request may close this issue.
See the full test logs here.
I can't quite tell from the logs which test is failing.
The text was updated successfully, but these errors were encountered: