Antoine Pitrou
Antoine Pitrou
"object 'tab' not found" is purely an R error? It looks weird.
Thanks for checking @paleolimbot . That's setting that might be fixed on the C++ side. I'll think about it.
Well, in any case I'll need to rebase and also complete the TODOs above.
Revision: 9e2bf2d5ac93e13d432ff6dbaea182c36e930d6f Submitted crossbow builds: [ursacomputing/crossbow @ signal-self-pipe-fork-0](https://github.com/ursacomputing/crossbow/branches/all?query=signal-self-pipe-fork-0) |Task|Status| |----|------| |test-alpine-linux-cpp|[](https://github.com/ursacomputing/crossbow/actions?query=branch:signal-self-pipe-fork-0-github-test-alpine-linux-cpp)| |test-build-cpp-fuzz|[](https://github.com/ursacomputing/crossbow/actions?query=branch:signal-self-pipe-fork-0-github-test-build-cpp-fuzz)| |test-conda-cpp|[](https://github.com/ursacomputing/crossbow/actions?query=branch:signal-self-pipe-fork-0-github-test-conda-cpp)| |test-conda-cpp-valgrind|[](https://dev.azure.com/ursacomputing/crossbow/_build/latest?definitionId=1&branchName=signal-self-pipe-fork-0-azure-test-conda-cpp-valgrind)| |test-debian-10-cpp-amd64|[](https://github.com/ursacomputing/crossbow/actions?query=branch:signal-self-pipe-fork-0-github-test-debian-10-cpp-amd64)| |test-debian-10-cpp-i386|[](https://github.com/ursacomputing/crossbow/actions?query=branch:signal-self-pipe-fork-0-github-test-debian-10-cpp-i386)| |test-debian-11-cpp-amd64|[](https://github.com/ursacomputing/crossbow/actions?query=branch:signal-self-pipe-fork-0-github-test-debian-11-cpp-amd64)| |test-debian-11-cpp-i386|[](https://github.com/ursacomputing/crossbow/actions?query=branch:signal-self-pipe-fork-0-github-test-debian-11-cpp-i386)| |test-fedora-35-cpp|[](https://github.com/ursacomputing/crossbow/actions?query=branch:signal-self-pipe-fork-0-github-test-fedora-35-cpp)| |test-ubuntu-18.04-cpp|[](https://github.com/ursacomputing/crossbow/actions?query=branch:signal-self-pipe-fork-0-github-test-ubuntu-18.04-cpp)| |test-ubuntu-18.04-cpp-release|[ |Task|Status| |----|------| |test-alpine-linux-cpp|[](https://github.com/ursacomputing/crossbow/actions?query=branch:signal-self-pipe-fork-1-github-test-alpine-linux-cpp)| |test-build-cpp-fuzz|[](https://github.com/ursacomputing/crossbow/actions?query=branch:signal-self-pipe-fork-1-github-test-build-cpp-fuzz)| |test-conda-cpp|[](https://github.com/ursacomputing/crossbow/actions?query=branch:signal-self-pipe-fork-1-github-test-conda-cpp)| |test-conda-cpp-valgrind|[](https://dev.azure.com/ursacomputing/crossbow/_build/latest?definitionId=1&branchName=signal-self-pipe-fork-1-azure-test-conda-cpp-valgrind)| |test-debian-10-cpp-amd64|[](https://github.com/ursacomputing/crossbow/actions?query=branch:signal-self-pipe-fork-1-github-test-debian-10-cpp-amd64)| |test-debian-10-cpp-i386|[](https://github.com/ursacomputing/crossbow/actions?query=branch:signal-self-pipe-fork-1-github-test-debian-10-cpp-i386)| |test-debian-11-cpp-amd64|[](https://github.com/ursacomputing/crossbow/actions?query=branch:signal-self-pipe-fork-1-github-test-debian-11-cpp-amd64)| |test-debian-11-cpp-i386|[](https://github.com/ursacomputing/crossbow/actions?query=branch:signal-self-pipe-fork-1-github-test-debian-11-cpp-i386)| |test-fedora-35-cpp|[](https://github.com/ursacomputing/crossbow/actions?query=branch:signal-self-pipe-fork-1-github-test-fedora-35-cpp)| |test-ubuntu-18.04-cpp|[](https://github.com/ursacomputing/crossbow/actions?query=branch:signal-self-pipe-fork-1-github-test-ubuntu-18.04-cpp)| |test-ubuntu-18.04-cpp-release|[![Github...
Le 31/10/2022 à 14:48, Dewey Dunnington a écrit : > Ok, I checked this again, and the errors that I get are: > > |/Users/dewey/Desktop/rscratch/arrow/cpp/src/arrow/status.cc:134: > Invalid: Signal stop source...
> The sequence is (for better or worse): Can you describe where the fork() call happens in that sequence?
I'll update this to use the at-fork facility introduced in https://github.com/apache/arrow/pull/14594
@github-actions crossbow submit -g conda