Unmark Z220 as untested

[d-wid]

Context: #1908

Apologies again for missing the test that led to my board being untested for many weeks. If you happen to at some point see it as a good idea to make it "tested" again here's a PR that can be merged to make it so.

Although, seeing as my board isn't labelled "unmaintained", am I right in assuming it's still being maintained anyway? I do find that worth more than the (un)tested label, fwiw.

It goes without saying you might want to see if I can reasonably I keep up in the future in a few rounds of testing testing-needed PRs before merging this.

[tlaurion]

Hey @d-wid :

• signed-off commits and DCO testing error of this PR: please read https://github.com/linuxboot/heads/blob/master/CONTRIBUTING.md#for-pull-requests
• Moving boards from testing to untested and vice versa: use Main Makefile's board.move_untested_to_tested helper

  heads/Makefile

  Line 894 in 13f55f4

  board.move_untested_to_tested:

  • That is, ./docker_repro.sh make BOARD=UNTESTED_XYZ board.move_untested_to_tested that was created to make this easier in situation exactly like this in the future; the tester needing to be able to move boards back to tested in a PR on their own timelines

---

The board having been moved to untested was under this commit: 382949d

Commit log said:

z220-cmt boards: move to untested with board.move_tested_to_untested helper, per notice at #1908 (comment)
Unfortunately the helper doesn't deal well with board inclusion: sed call is imperfect, and board config needs to be manually edited.

So in a perfect world, all boards would be tested in time and code redundancy would not be a problem in that case, but since we need to move boards back from tested to untested to unmaintained and abck and forth, @d-wid please remove board inclusion within each other (duplicate the whole entries making hotp board include HOTP being the only difference) so that moving this platform to untested/unmaintained becomes easy (as intended) in the future).

Where #1908 (comment) said:

Of all boards needing testing in OP(modified)

• t530 (xx30): @fhvyhjriur @3hhh
• z220-cmt (HP Z220 CMT): @d-wid
  Were not tested yet nor sign of life of when it could be tested soon. Since helpers are now in tree, I will push commit to move those back to untested, while still maintained (Someone will have to open issue to say they were tested when they are; the goal of which is not to say that those boards can be internally flashed by silent board owners without an external programmer to unbrick, as previously discussed under Bring back Lenovo Thinkpad T530 to supported/tested - images are working fine #1682 (comment) and led to notes added to https://osresearch.net/Prerequisites#supported-devices

---

Notes:

• this board is, AFAIK, only owned and used by you so you are kind of its maintainer, where my role for that board is to make sure that all code/config changes related to boards of the same CPU family/platform were applied on UNTESTED boards
• This is peculiar situation, where a board that is "supported" aka "maintained" should be used by multiple people to be a sustainable maintained effort over time.
• Here, minimally, putting this board back to tested (not UNTESTED) would mean that it won't brick when internally flashing. But for the rest, you would have to test features that were added since that board was moved to untested.
  • testing checklist from board porting guide https://osresearch.net/Porting/
  • moving target of commits between when board was moved to untested and master: 382949d...master
    • so 62 commits related PR to check impacts for this board, where master today is 13f55f4 so those same 62 commits can be checked with 382949d...13f55f4