Skip to content

Fix Possible Race Condition On Config Files During Testing #37

@awandke

Description

@awandke

I have gotten the following error, but I've been unable to replicate it. This means the error is probably non-deterministic and due to some kind of race condition. Perhaps it it failing to update to configuration because it is blocked by a currently running version of SeaBee?

This would be strange since I've altered the update config code to wait for permissions if it doesn't have them.

I got this bug on fedora 42: 6.15.9-201.fc42.x86_64, though I think the kernel version is unlikely to be the cause of the bug.

Run Verified Policy Tests
Error: Failed to update SeaBee saved config at configs/verified_policy.yaml
Operation not permitted (os error 1)
Error: Failed { msg: Some("Failed to update SeaBee config.\nstatus: exit status: 1") }
make[1]: *** [Makefile:29: policy-test] Error 1
make[1]: Leaving directory '/home/adwandk/seabee/tests'
make: *** [Makefile:87: test-ci] Error 2

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions