Package: faketime Version: 0.9.7-2 I was running pre-release tests of dgit: autopkgtest running the DEP-8 test suites, in an schroot. The test suite does faketime debchange ...
In one of my runs today, I got this error: + faketime @1515000000 dch -v 2.0-1 -m 'new upstream (did gbp import-orig)' sem_open: File exists I did `ipcs' and it shows only two `Semaphore Arrays'. (I have a lot of `Shared Memory Segments'.) AFAICT this error was transient even within the chroot (I think the next test reused the chroot; they certainly passed). I don't really have any other information. If you like I can run my tests in future with a modified version of faketime, but empirically, I have never seen this error before, so unless something has changed the failure rate is going to be one every several years in my environment. It may be easier to find the bug by code inspection. I did a web search for the error message and got this bug report from 2016: https://github.com/wolfcw/libfaketime/issues/96 But I'm basically never sigkilling my faketime processes. They will occasionally get a ^C or something, I guess. (Also, I'm not sure why this usage of faketime needs a semaphore at all, given that that in that bug the effect of the faketime wrapper can apparently be produced simply by setting env vars.) Ian. -- Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
