- From: Peter Linss via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 Mar 2023 23:59:59 +0000
- To: public-css-archive@w3.org
IIRC the test harness just needs the manifest file from the build system. There may be some dependency on the flat structure of the build output, but I'm not sure if that matters anymore (it's been a while, so I'd have to dig into the code), id so it would probably be east to remove. I do know that the builds started failing a while back and I haven't had the bandwidth to look into it, but all the relevant code is online so anyone can do it. To me the bigger concern is that the build code as I last remember it was heavily dependent on the metadata stored in the tests. I don't know what the status of that these days is and what kind of metadata is available from in WPT. Updating/maintaining that may be a bigger deal. If we do keep the harness, the manifest generator (part of the current build process) also needs to be ported over to Python 3, I really don't want to have to install Python 2 on the new server. There's also the matter of ensuring the old (PHP5) harness code will run on PHP8 for the new server, it might 'just work' or might need some updating. -- GitHub Notification of comment by plinss Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6896#issuecomment-1482064478 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 24 March 2023 00:00:01 UTC