-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Catch GR test failing #213
Conversation
d2464a2
to
31d9289
Compare
This error appears
which seems is happening because node
and only observed until now for |
A second failure is observed
which is happening on the setup and before even GR test starts |
31d9289
to
1f5784b
Compare
@fedepaol the investigation showed that there is an option
the default value was 5, and that seems to make the test failing due to timing issues. I can not find any doc around that in the official doc. When value 20, the ci runs for 50 times per test (ipv4,ipv6,dual,helm) without a failure* When value is 0, running the test once locally fails in the same way.
|
030f190
to
1f5784b
Compare
that failure looks different, looking the logs
seems all nodes were not healthy and GR ended, test stopped.
|
1f5784b
to
e78d8e2
Compare
99fd53d
to
9daae72
Compare
9daae72
to
84fbda8
Compare
e7c6703
to
0481986
Compare
7a15bec
to
421159c
Compare
b945138
to
a1ce9c5
Compare
- debug in watchfrr - capture coredump on bgp crashes - increase prefix scale on ipv4 Signed-off-by: karampok <karampok@gmail.com>
Signed-off-by: karampok <karampok@gmail.com>
a1ce9c5
to
30925f1
Compare
/kind flake
What this PR does / why we need it:
Special notes for your reviewer:
Release note: