ci: use persistent worker for fuzz_msan #132

1. 
   maflcko commented at 4:14 pm on June 2, 2023: contributor
2. maflcko force-pushed on Jun 2, 2023
3. ci: use persistent worker for fuzz_msan f4f6b38105
4. maflcko force-pushed on Jun 2, 2023
5. 
   dergoegge commented at 9:14 am on June 5, 2023: member

   wanna restart the msan job? looks like a spurious failure
6. 
   maflcko commented at 9:26 am on June 5, 2023: contributor

   Not sure how that could happen. Maybe a podman bug, because the container should have been killed (and thus removed)?

    0++ echo 'Restart docker before run to stop and clear all containers started with --rm'
    1Restart docker before run to stop and clear all containers started with --rm
    2++ podman container kill --all
    3++ echo 'Prune all dangling images'
    4Prune all dangling images
    5++ docker image prune --force
    6Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
    7+++ docker run --rm --interactive --detach --tty --mount type=bind,src=/tmp/cirrus-build/bitcoin-core,dst=/ro_base,readonly --mount type=volume,src=ci_native_fuzz_msan_ccache,dst=/tmp/ccache_dir --mount type=volume,src=ci_native_fuzz_msan_depends,dst=/tmp/cirrus-build/bitcoin-core/depends --mount type=volume,src=ci_native_fuzz_msan_previous_releases,dst=/tmp/cirrus-build/bitcoin-core/releases/x86_64-pc-linux-gnu -w /tmp/cirrus-build/bitcoin-core --env-file /tmp/env --name ci_native_fuzz_msan ci_native_fuzz_msan
    8Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
    9time="2023-06-02T21:04:01Z" level=warning msg="The input device is not a TTY. The --tty and --interactive flags might not work properly"
   10Error: error creating container storage: the container name "ci_native_fuzz_msan" is already in use by "fb7292217b6fc8c64dc5076beb55bab0a48a7b3649a99d6179256d293ea711fa". You have to remove that container to be able to reuse that name.: that name is already in use
   

7. 
   maflcko commented at 7:02 am on June 6, 2023: contributor

   Anything left to do here?
8. fanquake merged this on Jun 6, 2023
9. fanquake closed this on Jun 6, 2023

   ---

Contributors
maflcko dergoegge