Skip to content

Contest: prepare HW split - #100

Open
matttbe wants to merge 3 commits into
linux-netdev:mainfrom
matttbe:contest-split-hw
Open

Contest: prepare HW split#100
matttbe wants to merge 3 commits into
linux-netdev:mainfrom
matttbe:contest-split-hw

Conversation

@matttbe

@matttbe matttbe commented Sep 10, 2026

Copy link
Copy Markdown
Member

This prepares the future split, dealing with HW results in a different 'contest'.

The plan is:

  • contest/results-collector.py:
    • launch a second service, from a subdir, with different settings, e.g. remote + branch_url input, output file/dir/cache
    • split remote_db.json
    • use the same DB: from what I saw, it should be fine: on the HW side, they have different branches and remotes. So OK?
  • pw_contest.py:
    • launch a second service, from a subdir, with different settings, e.g. log, pw check name, input json file from results-collector.py
  • faker: not needed any more, see the last commit
  • UI:
    • nothing to do if I'm not mistaken because the DB will be filled the same way (but from two different services). Only PW will be affected.

Note: of course, this shouldn't be deployed until the corresponding modifications are done on the hosts.

To prepare a split between HW and the rest.

Signed-off-by: Matthieu Baerts <matttbe@kernel.org>
This file is read by another service (faker), possibly simultaneously.

Signed-off-by: Matthieu Baerts <matttbe@kernel.org>
With the split of the virtual and HW tests, it is no longer needed:

 - The two 'info' files no longer need to be combined: there will be two
   contest services

 - The 'faker' branches [1] don't seem to be used anymore

So drop the whole service, not to be confused by it.

Link: https://netdev-ctrl.bots.linux.dev/faker/results.json [1]
Signed-off-by: Matthieu Baerts <matttbe@kernel.org>
@matttbe
matttbe requested a review from kuba-moo September 10, 2026 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant