Add test down interfaces #116
No reviewers
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-testcases#116
Loading…
Reference in a new issue
No description provided.
Delete branch "d.zayakin/frostfs-testcases:down-interfaces-test"
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?
Signed-off-by: Dmitriy Zayakin d.zayakin@yadro.com
28316f94f6
to5e64e222c5
@ -325,0 +346,4 @@
simple_object_size: ObjectSize,
delete_file_after_test: None,
restore_down_interfaces: None,
data: tuple,
That's not
data
:)looks like it's
interface
thanks! Done
@ -325,0 +337,4 @@
@pytest.mark.interfaces
@pytest.mark.baremetal
@pytest.mark.parametrize("data", [(Interfaces.DATA_O, Interfaces.DATA_1), (Interfaces.DATA_1, Interfaces.DATA_O)])
also, why not
?
This is also possible, just a slightly different approach. I don’t see much of a difference from what I did now.
Your approach leads to redundant line of code
@ -325,0 +393,4 @@
@pytest.mark.interfaces
@pytest.mark.baremetal
@pytest.mark.parametrize("internal", [Interfaces.INTERNAL_0, Interfaces.INTERNAL_1])
same
@ -325,0 +437,4 @@
cid=cid,
shell=self.shell,
endpoint=self.cluster.default_rpc_endpoint,
timeout="60s",
Why explicit timeout here?
This time may be needed to synchronize internal components.
5e64e222c5
tod960a28290
d960a28290
tob05125af26
b05125af26
to57e954ab4c