Testing FRRouting Pull Requests with netlab
The author occasionally finds bugs in FRRouting, which are quickly addressed by developers, and testing fixes is simplified using netlab with an existing topology file.
MAIN POINTS
- Bugs in FRRouting are discovered infrequently but are quickly fixed by developers.
- Developers often request testing of pull requests after fixing bugs.
- Netlab simplifies the process of testing fixes for FRRouting bugs.
- An existing topology file is required to reproduce and test the bug.
TAKEAWAYS
- FRRouting developers are responsive and efficient in addressing bugs.
- Testing fixes in FRRouting can be streamlined with the use of netlab.
- Having a topology file is essential for reproducing and testing bugs.
- The process of testing fixes is straightforward and well-documented.