3 Commits

Author	SHA1	Message	Date
Juliusz Sosinowicz	844852202b	.github: bump JavaScript actions to Node.js 24 runtimes ... GitHub Actions now emits "Node.js 20 actions are deprecated" warnings: actions are forced to Node.js 24 by default starting 2026-06-16, and Node.js 20 is removed from the runners on 2026-09-16. Update every JavaScript action referenced by the workflows and the local composite actions to the lowest release that runs on Node.js 24: actions/checkout v4 -> v5 actions/checkout (SHA pin) v4.1.7 -> v5 actions/upload-artifact v4 -> v6 (v5 still Node.js 20) actions/download-artifact v4 -> v7 (v5/v6 still Node.js 20) actions/cache[/restore|/save] v4 -> v5 actions/setup-python v5 -> v6 actions/github-script v7 -> v8 docker/setup-buildx-action v3 -> v4 docker/build-push-action v5 -> v7 (v6 still Node.js 20) docker/login-action v3 -> v4 microsoft/setup-msbuild v2 -> v3 open-watcom/setup-watcom v0 -> v1 Actions already running on Node.js 24 (jwlawson/actions-setup-cmake, shogo82148/actions-setup-perl, msys2/setup-msys2, dorny/paths-filter) are left unchanged. These bumps are runtime-only; no workflow uses an input or output removed by the new majors, and v4-format artifacts remain compatible across the upload v6 / download v7 backends.	2026-06-15 18:09:04 +00:00
David Garske	7f80896033	CI optimizations ... - Skip CI for draft PRs and redundant master-push re-runs; membrowse nightly. - Add smoke test (8 configs, CFLAGS=-Werror, post-merge tree, fail-fast on conflicts). - Add wait-for-smoke composite action for downstream CI gating. - Add check-source-text + bash -n + shellcheck workflow (script in make dist). - Cache apt-get update in install-apt-deps composite on cache hit.	2026-05-21 13:19:29 -07:00
Andrew Hutchings	7b89d82b35	Fix mem_track.h compile failure on multi-threaded non-Linux builds ... The memLock mutex and #include <pthread.h> in mem_track.h were declared under #ifdef DO_MEM_LIST (Linux/macOS/Zephyr only), but referenced under the broader guard !defined(SINGLE_THREADED) && \ (defined(DO_MEM_LIST) || defined(DO_MEM_STATS)) Since DO_MEM_STATS is defined whenever WOLFSSL_TRACK_MEMORY + USE_WOLFSSL_MEMORY are set without WOLFSSL_STATIC_MEMORY, any non-Linux/Mac/Zephyr multi-threaded build failed to compile with implicit pthread_mutex_lock declarations and undeclared memLock. Replace the raw pthread mutex with wolfSSL's portable mutex API (wc_InitMutex / wc_LockMutex / wc_UnLockMutex / wc_FreeMutex) so locking works on every platform wolfSSL already ports to. InitMemoryTracker now calls wc_InitMutex before wolfSSL_SetAllocators installs TrackMalloc, guarded by a memLockInit flag for idempotency. CleanupMemoryTracker calls wc_FreeMutex after restoring the default allocators so no in-flight allocation races a freed mutex. The four mutex guards in TrackMalloc/TrackFree and the two in InitMemoryTracker/ ShowMemoryTracker are unified on the same condition as the memLock declaration itself. ZD #21763	2026-05-11 16:20:35 +01:00