Skip to content

Fix/revert ipv4 mapped ipv6 stuff 10.1 v2 #449

Fix/revert ipv4 mapped ipv6 stuff 10.1 v2

Fix/revert ipv4 mapped ipv6 stuff 10.1 v2 #449

Triggered via pull request August 16, 2024 02:09
Status Failure
Total duration 42s
Artifacts

commitlint.yml

on: pull_request
Check if the commits meet the requirements of the guidelines
31s
Check if the commits meet the requirements of the guidelines
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
Check if the commits meet the requirements of the guidelines
You have commit messages with errors ⧗ input: bgpd: backpressure - log error for evpn when route install to zebra fails. log error for evpn in case route install to zebra fails. Ticket :#3992392 Signed-off-by: Rajasekar Raja <[email protected]> ✖ header must not be longer than 72 characters, current length is 74 [header-max-length] ✖ subject may not end with full stop [subject-full-stop] ✖ found 2 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: topotests: bgp_nexthop_mp_ipv4_6, test ipv4-mapped Test that a IPv4-mapped IPv6 is sent from a peer that has no global IPv6 address. Signed-off-by: Louis Scalbert <[email protected]> ✖ type must be one of [babeld, bfdd, bgpd, build, doc, docker, eigrpd, fpm, isisd, ldpd, lib, mgmtd, multi, nhrpd, ospf6d, ospfd, pathd, pbrd, pimd, pim6d, ripd, ripngd, sharpd, staticd, tests, tools, vtysh, vrrpd, yang, zebra, all] [type-enum] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
Check if the commits meet the requirements of the guidelines
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/