diff --git a/scripts/kernel-test.sh b/scripts/kernel-test.sh index 031c11342d..256de380c1 100755 --- a/scripts/kernel-test.sh +++ b/scripts/kernel-test.sh @@ -31,12 +31,14 @@ IMAGE="${IMAGE:-orcacad-deps}" # this fork at it makes the two silently trade build artefacts. docker-iter-build.sh had the # identical defect and was fixed to orcacad_buildcache; this script was missed. VOL="${BUILD_VOL:-orcacad_kerneltest}" -# Two pre-existing failures are excluded by default (see [known-broken] in -# test_caddocument.cpp): one of them SIGABRTs inside the vendored solver and takes the +# ONE pre-existing failure is excluded by default (see [known-broken] in +# test_caddocument.cpp): it SIGABRTs inside the vendored solver and takes the # whole process down, so without this exclusion a green run is simply unreachable and the -# suite stops after ~12 of 32 cases. Both are also tagged [NotWorking], the ctest label -# the mainline fork's CI excludes, so they no longer redden its Unit Tests job on every -# commit; they stay tracked as snaporca-tkz and snaporca-kzy rather than as CI noise. +# suite stops after ~12 of 32 cases. It is also tagged [NotWorking], the ctest label the +# mainline fork's CI excludes, so it no longer reddens the Unit Tests job on every commit; +# it stays tracked as snaporca-tkz rather than as CI noise. The internal-thread case that +# used to sit alongside it is gone from this exclusion: its geometry was correct and the +# test's reference was wrong (snaporca-kzy), so it now runs like any other. TAGS="${TAGS:-[CadDocument]~[known-broken]}" HOST=""