public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Max Carrara" <m.carrara@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH v2 pve-network 0/5] SDN tests in sbuild
Date: Mon, 25 Mar 2024 14:24:43 +0100	[thread overview]
Message-ID: <D02V4L8SIP11.1L2BJAE93UENN@proxmox.com> (raw)
In-Reply-To: <20240307151319.301984-2-s.lendl@proxmox.com>

On Thu Mar 7, 2024 at 4:13 PM CET, Stefan Lendl wrote:
> Extract and mock functions that otherwise access system files which is not
> possible in a clean sbuild environment.
> Namely /etc/network/interfaces as well as /etc/frr/frr.config.local
> Disabling DNS tests
>
> Changes v1 -> v2:
> * Disabled DNS tests because they fail
>

Looked through it all and ran the tests manually and also indirectly via
builds - looks pretty good to me! Always fond of making things more
testable! :)

There are some minor comments inline - but one important thing: The DNS
tests are passing for me. Maybe double-check if they pass for you now
too; if that's the case, patch #4 can just be dropped, as mentioned in
my comment.

Otherwise:

Reviewed-by: Max Carrara <m.carrara@proxmox.com>
Tested-by: Max Carrara <m.carrara@proxmox.com>

>
> Stefan Lendl (5):
>   refactor(controllers): extract read_etc_network_interfaces
>   refactor(evpn): extract read_local_frr_config
>   tests: mocking more functions to avoid system access
>   tests: disable failing DNS tests
>   tests: run tests in sbuild
>
>  src/Makefile                                  |  2 +-
>  src/PVE/Network/SDN/Controllers.pm            | 16 ++++++---
>  src/PVE/Network/SDN/Controllers/EvpnPlugin.pm | 10 ++++--
>  src/test/Makefile                             |  2 +-
>  src/test/run_test_zones.pl                    | 36 ++++++++++++++++++-
>  5 files changed, 56 insertions(+), 10 deletions(-)





  parent reply	other threads:[~2024-03-25 13:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 15:13 Stefan Lendl
2024-03-07 15:13 ` [pve-devel] [PATCH v2 pve-network 1/5] refactor(controllers): extract read_etc_network_interfaces Stefan Lendl
2024-03-25 13:19   ` Max Carrara
2024-03-07 15:13 ` [pve-devel] [PATCH v2 pve-network 2/5] refactor(evpn): extract read_local_frr_config Stefan Lendl
2024-03-25 13:20   ` Max Carrara
2024-03-07 15:13 ` [pve-devel] [PATCH v2 pve-network 3/5] tests: mocking more functions to avoid system access Stefan Lendl
2024-03-25 13:21   ` Max Carrara
2024-03-07 15:13 ` [pve-devel] [PATCH v2 pve-network 4/5] tests: disable failing DNS tests Stefan Lendl
2024-03-25 13:21   ` Max Carrara
2024-03-07 15:13 ` [pve-devel] [PATCH v2 pve-network 5/5] tests: run tests in sbuild Stefan Lendl
2024-03-25 13:24 ` Max Carrara [this message]
2024-04-02 11:10   ` [pve-devel] [PATCH v2 pve-network 0/5] SDN " Stefan Lendl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D02V4L8SIP11.1L2BJAE93UENN@proxmox.com \
    --to=m.carrara@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal