Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/dependabot.yml
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@ updates:

# TMT component-test runtime
- package-ecosystem: "pip"
directory: "/internal/app/azldev/cmds/component"
directory: "/internal/tmt"
schedule:
interval: "weekly"
cooldown:
Expand Down
4 changes: 2 additions & 2 deletions docs/developer/how-to/testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,11 +73,11 @@ image-construction test; ordinary scenario and e2e containers remain unchanged.
### Virtual TMT provisioning regression

`mage e2e -target=tmt` builds the current Azure Linux image, then runs the real
`azldev component test` flow with TMT 1.78.0, testcloud 0.12.0, and a tiny
`azldev component test` flow with the pinned TMT/testcloud runtime and a tiny
test-only probe RPM. The non-privileged TMT runner maps `/dev/kvm`, uses private
session-libvirt state, and retains diagnostics under `out/tmt-virtual-e2e/`.
Production and test dependency pins share
`internal/app/azldev/cmds/component/requirements.txt`, which Dependabot tracks.
`internal/tmt/requirements.txt`, which Dependabot tracks.

This regression is temporarily quarantined while the known testcloud readiness
failure is fixed. The normal `mage e2e` suite compiles the test but skips it;
Expand Down
Loading
Loading