Lou Berger
Lou Berger
> @louberger -> I don't see anything that should cause your CI to fail, can you help us understand what went wrong? agree - rerunning
this is changing rr updae route selection...
sorry for the delay on this one, it looks like it is actually changing some underlying behavior the test that is failing is in a CE/PE config and routes are...
> Hi @pguibert6WIND, > > ``` > I think the real use case is something wiser, like the next-hop resolution > does not see any labels and stops, whereas the...
6.0 and 7.0 both look unchanged in the labn ci. -which only covers bgp and bgp with l3vpns
> seeing some material changes to BGP advertisements in LabN Ci is this expected? actually, this failed for a different reason -- (comment applied to 11582) still an issue though...
Program terminated with signal SIGSEGV, Segmentation fault. #0 raise (sig=sig@entry=11) at ../sysdeps/unix/sysv/linux/raise.c:51 [Current thread is 1 (Thread 0x7f07ed2e5200 (LWP 2757))] (gdb) #0 raise (sig=sig@entry=11) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x00005646c47cd429 in core_handler...
latest core Program terminated with signal SIGSEGV, Segmentation fault. #0 raise (sig=sig@entry=11) at ../sysdeps/unix/sysv/linux/raise.c:51 [Current thread is 1 (Thread 0x7f7628714200 (LWP 28509))] (gdb) #0 raise (sig=sig@entry=11) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x0000561e00024409...
would be nice to have a topotest for this