tests: record AFP create file smoke success
All checks were successful
Source release / source-package (push) Successful in 48s

This commit is contained in:
Mario Fetka
2026-05-30 19:47:40 +00:00
parent 434de903bd
commit 3b3a378a22
2 changed files with 21 additions and 5 deletions

18
TODO.md
View File

@@ -488,13 +488,21 @@ Endpoint order:
Linux smoke helper creates both legacy and AFP 2.0 files under the tested
parent, verifies the returned AFP file ID with Entry ID From Path Name, and
keeps local cleanup best-effort because AFP Delete is still pending.
- Runtime status: create-file smoke is added but still needs a build-server
runtime confirmation before recording success.
- Runtime status: the create-file smoke has been verified. The run created
`SYS:PUBLIC/atst0` through legacy AFP Create File (`0x02`) and
`SYS:PUBLIC/atst02` through AFP 2.0 Create File (`0x0e`); both returned
nwatalk/fallback AFP file IDs (`0x333bee1c` and `0x4e329102`) and were
re-verified with AFP Entry ID From Path Name. The same run ended with
`failures=2` only because earlier create-directory leftovers
(`AFPTST0`/`AFPTST02`) already existed and cannot be removed by the
unprivileged local test user until AFP Delete exists; the create-file probes
themselves completed successfully.
- Next implement AFP Delete (`0x03`) through the existing NetWare delete/erase
policy path so the smoke suite can clean up its own temporary directories and
files through the server instead of relying on local Unix removal.
- Then implement AFP Rename (`0x07`) through the existing NetWare rename/move
path, preserving FinderInfo/xattrs and checking Entry ID behavior.
- Keep AFP Delete (`0x03`) and Get Macintosh Info On Deleted File (`0x13`) for
last. Delete must only be enabled through the existing NetWare delete/erase
policy path and smoke-tested on self-created temporary files.
- Keep Get Macintosh Info On Deleted File (`0x13`) for last.
## Deferred / optional protocol work

View File

@@ -253,6 +253,14 @@ unprivileged Unix user while mars_nwe creates the file as the server-side
identity. Use `--create-file-name NAME` to override the default leaf name;
rerunning with the same explicit name may fail if a previous file still exists.
Runtime status: the build-server smoke run verified both create-file variants.
Legacy AFP Create File (`0x02`) created `SYS:PUBLIC/atst0` and returned
`0x333bee1c`; AFP 2.0 Create File (`0x0e`) created `SYS:PUBLIC/atst02` and
returned `0x4e329102`. Both IDs were re-read through AFP Entry ID From Path
Name. The overall run still reported `failures=2`, but those failures were the
pre-existing create-directory names `AFPTST0` and `AFPTST02`; the create-file
checks themselves succeeded.
## AFP Entry ID smoke test
`afp_entry_id_smoke` sends the WebSDK-documented NetWare AFP request: