Don't traceback on unkown sections.

[s0undt3ch]

Thanks for submitting a PR, your contribution is really appreciated!

Here's a quick checklist that should be present in PRs:

• Add a new news fragment into the changelog folder
  • name it $issue_id.$type for example (588.bugfix)
  • if you don't have an issue_id change it to the pr id after creating the pr
  • ensure type is one of removal, feature, bugfix, vendor, doc or trivial
  • Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files."
• Target: for bugfix, vendor, doc or trivial fixes, target master; for removals or features target features;
• Make sure to include reasonable tests for your change if necessary

Unless your change is a trivial or a documentation fix (e.g., a typo or reword of a small section) please:

• Add yourself to AUTHORS, in alphabetical order;

[coveralls]

Coverage remained the same at 92.628% when pulling 42c1f85 on s0undt3ch:issues/3184 into 570edb4 on pytest-dev:master.

[nicoddemus]

Thanks a lot @s0undt3ch!

[s0undt3ch]

Anytime!

[s0undt3ch]

So, when is this getting release on the wild?

[nicoddemus]

This week we should release 3.4.1. 😁

[s0undt3ch]

Awesome! It caused some minor grief with at least one of my coworkers :)