CI: run pytest and coverage tests inside ephemeral VM in the "builder" VM (nested) #103

Merged

houkime merged 5 commits from ci-vm-for-pytest into master

2024-03-18 12:07:54 +02:00

alexoundos commented

2024-03-09 02:16:58 +02:00

Collaborator

Simply nix flake check -L is invoked (same as locally available).

Simply `nix flake check -L` is invoked (same as locally available).

houkime was assigned by alexoundos

2024-03-09 02:16:58 +02:00

inex was assigned by alexoundos

2024-03-09 02:16:58 +02:00

alexoundos added 3 commits 2024-03-09 02:16:58 +02:00

continuous-integration/drone/push Build is failing Details

108305a264 ci: run pytest and coverage as part of nix flake check in VM

continuous-integration/drone/push Build is failing Details

57a9f588e8 fix: future mock are now more in the future

continuous-integration/drone/push Build was killed Details

77f8856515 fix: Mark md5 as not used for security

alexoundos commented

2024-03-09 02:20:28 +02:00

Poster

Collaborator

What to do with the redis port number? Is it used now?
It is currently defined in two places:

6389 as environment variable here: 77f8856515/.drone.yml (L13)
6379 as redis systemd service parameter here: 77f8856515/flake.nix (L126)

What to do with the redis port number? Is it used now? It is currently defined in two places: * `6389` as environment variable here: https://git.selfprivacy.org/SelfPrivacy/selfprivacy-rest-api/src/commit/77f8856515ef3e085edc4dadda257b9eac1ed41c/.drone.yml#L13 * `6379` as `redis` systemd service parameter here: https://git.selfprivacy.org/SelfPrivacy/selfprivacy-rest-api/src/commit/77f8856515ef3e085edc4dadda257b9eac1ed41c/flake.nix#L126

alexoundos commented

2024-03-09 02:22:34 +02:00

Poster

Collaborator

Do we need to export coverage xml somewhere after the test has ended?

Do we need to export coverage `xml` somewhere after the test has ended?

alexoundos requested review from houkime 2024-03-09 02:25:06 +02:00

houkime was unassigned by alexoundos

2024-03-09 02:25:15 +02:00

houkime commented

2024-03-13 15:12:34 +02:00

Collaborator

What to do with the redis port number? Is it used now?
It is currently defined in two places:

6389 as environment variable here: 77f8856515/.drone.yml (L13)

6379 as redis systemd service parameter here: 77f8856515/flake.nix (L126)

We no longer test with a port.

> What to do with the redis port number? Is it used now? > It is currently defined in two places: > * `6389` as environment variable here: https://git.selfprivacy.org/SelfPrivacy/selfprivacy-rest-api/src/commit/77f8856515ef3e085edc4dadda257b9eac1ed41c/.drone.yml#L13 > * `6379` as `redis` systemd service parameter here: https://git.selfprivacy.org/SelfPrivacy/selfprivacy-rest-api/src/commit/77f8856515ef3e085edc4dadda257b9eac1ed41c/flake.nix#L126 We no longer test with a port.

houkime requested changes 2024-03-15 13:38:47 +02:00

houkime left a comment

Collaborator

Delete remaining port settings, we do not use them anymore

alexoundos added 1 commit 2024-03-15 14:11:49 +02:00

continuous-integration/drone/push Build was killed Details

87516bfe9a flake: VM test: remove Redis service port number setting

alexoundos commented

2024-03-15 14:13:14 +02:00

Poster

Collaborator

Delete remaining port settings, we do not use them anymore

@houkime, deleted. 87516bfe9a.

> Delete remaining port settings, we do not use them anymore @houkime, deleted. 87516bfe9a64024fdbbbe5556646b48213526047.

alexoundos force-pushed ci-vm-for-pytest from 87516bfe9a to 53ec774c90

2024-03-15 14:23:57 +02:00

Compare

alexoundos changed title from ~~WIP: CI: run pytest and coverage tests inside ephemeral VM in the "builder" VM (nested)~~ to CI: run pytest and coverage tests inside ephemeral VM in the "builder" VM (nested)

2024-03-15 14:25:41 +02:00

alexoundos added 1 commit 2024-03-15 22:18:10 +02:00