tests' memory metadata #704
Labels
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#224 automated dev-ops workflows
fediversity/fediversity
#362 NixOS tests break when CI runs them in parallel
fediversity/fediversity
Reference
fediversity/fediversity#704
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As a Fediversity maintainer,
I want for tests to expose metadata about their required amount of memory,
so that we might parallelize tests (c.f. #362) in such a way as to efficiently allocate resources for test runs.
implementation notes
virtualisation.memorySize, #721 may remove thatrequiredMemoryon checks for CI memory-aware scheduling #799