Closed Ktmi closed 6 months ago
I keep getting weird behavior out of this on end to end tests. I can't seem to figure out what went wrong. It seems, that in the e2e tests, events aren't getting properly passed around, though I can't wholly confirm that's the cause. When I run kytos normally, events seem to get passed around as they should. In the mean time, I'm going to keep this patch running in my environment until I can figure out why it doesn't work correctly in end to end tests.
I keep getting weird behavior out of this on end to end tests. I can't seem to figure out what went wrong. It seems, that in the e2e tests, events aren't getting properly passed around, though I can't wholly confirm that's the cause. When I run kytos normally, events seem to get passed around as they should. In the mean time, I'm going to keep this patch running in my environment until I can figure out why it doesn't work correctly in end to end tests.
Interesting. OK. Btw, we currently do have a few sdntrace failing tests though https://github.com/kytos-ng/kytos-end-to-end-tests/issues/255 that @gretelliz will fix, but sounds like you've hit a more generalized problem.
@Ktmi, based on what we just discussed on our weekly meeting, the easiest route here is to set it as a draft, until the e2e issue is sorted, OK. I'll go ahead and mark it as a draft.
Gonna close this for now. It's a nice idea, but the strange technical issues that are popping up make it untenable.
Summary
This converts KytosEvent into a dataclass with type annotations. Additionally it changes it so that it is now considered a bug for an event to not have a
name
set.Local Tests
Seems to work correctly. Can create evcs and have them interrupted by maintenance windows.
End To End Tests
These seem to fail pretty badly, and I don't understand what's going on here.