0.2.0: the tests are given an implementation, and the example is asserted against wc

Every test in this package failed to link. The package declares against the
interface and links against no implementation, which is correct — a consumer
chooses one — but its own tests run, and running requires definitions. The
implementation is now a development dependency, selected by the platform the
tests run upon.

The diagnostic was the one clause 4.2 of the specification describes: the
package compiled, the link failed, and the linker named sixteen undefined
operations. That is later than a compilation failure and it is legible, which
is what the clause claims for it. This is the first occasion on which the claim
was tested by something other than a deliberate demonstration.

The step that ran an example ran a program this repository does not contain and
asserted lines it does not print. It is replaced by one that runs the example
that is here and compares its output against the system's own counter, so the
assertion is that the program produced the right answer rather than that it
produced an answer.

The assertion that the suites ran is derived from the files present rather than
written out, for the same reason it is elsewhere: a hand-written list names the
suites that existed when it was written.

Author: speak-agent

.github/workflows/ci.yml

@@ -38,16 +38,44 @@ jobs:
       - name: Tests
         run: |
           mcpp test 2>&1 | tee tests.log
-          # A suite that discovered nothing reports success, so each case is
-          # asserted to have run.
-          grep -q 'paths ... ok'  tests.log
-          grep -q 'files ... ok'  tests.log
-          grep -q 'mutex ... ok'  tests.log
 
+          # A suite that discovered nothing reports success, so every suite is
+          # asserted to have run. The list is derived from the files present
+          # rather than written out here: a hand-written list names the suites
+          # that existed when it was written, and one added afterwards escapes
+          # the assertion silently.
+          missing=0
+          for f in tests/*.cpp; do
+            name="$(basename "$f" .cpp)"
+            if ! grep -q "^$name \.\.\. ok" tests.log; then
+              echo "suite did not run, or did not pass: $name" >&2
+              missing=1
+            fi
+          done
+          test "$missing" -eq 0
+
+      # The claim this package makes is that a program above it reads a file by
+      # global path, consults a variable, measures an interval and starts
+      # another program without containing any of that. The program is compared
+      # against the system's own counter, so the assertion is that it produced
+      # the right answer rather than that it produced an answer.
+      #
+      # The previous form of this step asserted three lines from a different
+      # example, in a directory this repository does not contain. It had never
+      # run: the step before it failed first, and a step that never runs asserts
+      # nothing while appearing to.
       - name: An ordinary program runs above the library
-        working-directory: examples/hello
+        working-directory: examples/wordcount
         run: |
-          mcpp run 2>&1 | tee run.log
-          grep -q 'openkal: hello' run.log
-          grep -q 'openkal: allocation succeeded' run.log
-          grep -q 'openkal: vectored writes unavailable' run.log
+          printf 'alpha beta\ngamma\n' > sample.txt
+          expected="$(wc < sample.txt | tr -s ' ' | sed 's/^ //')"
+          WORDCOUNT_VERBOSE=1 mcpp run -- sample.txt 2>&1 | tee run.log
+
+          lines="$(sed -n 's/^lines \([0-9]*\) words \([0-9]*\) bytes \([0-9]*\)$/\1 \2 \3/p' run.log)"
+          test -n "$lines" || { echo "the program printed no count" >&2; exit 1; }
+          echo "wordcount: $lines"
+          echo "wc:        $expected"
+          test "$lines" = "$expected"
+
+          # The variable was consulted, and the interval was measured.
+          grep -q 'elapsed .* nanoseconds' run.log

examples/wordcount/mcpp.toml

@@ -6,7 +6,7 @@ version = "0.1.0"
 openkal-libc = { path = "../.." }
 
 [target.'cfg(os = "linux")'.dependencies]
-openkal-linux = "0.3.0"
+openkal-linux = "0.4.0"
 
 [target.'cfg(os = "macos")'.dependencies]
-openkal-macos = "0.1.0"
+openkal-macos = "0.2.0"

mcpp.toml

@@ -1,11 +1,25 @@
 [package]
 namespace   = "mcpplibs"
 name        = "openkal-libc"
-version     = "0.1.0"
+version     = "0.2.0"
 description = "A C library above openkal rather than above a kernel. Porting it once causes the software above it to run on every openkal implementation, which is the claim the specification makes and this package tests."
 license     = "Apache-2.0"
 authors     = ["mcpplibs"]
 repo        = "https://github.com/mcpplibs/openkal-libc"
 
 [dependencies]
-openkal = "0.3.0"
+openkal = "0.4.0"
+
+# The library declares against the interface and links against no
+# implementation: a consumer of it chooses one. Its own tests run, and running
+# requires definitions, so an implementation is a development dependency and is
+# selected by the platform the tests run upon.
+#
+# Its absence is why every test in this package failed to link while the package
+# itself built: the diagnostic named the undefined operations, which is what
+# clause 4.2 of the specification describes.
+[target.'cfg(os = "linux")'.dev-dependencies]
+openkal-linux = "0.4.0"
+
+[target.'cfg(os = "macos")'.dev-dependencies]
+openkal-macos = "0.2.0"