Secondary file name patterns aren't used if the first doesn't match

[pnuu]

Describe the bug
Reading GOES ABI data from Eumetcast with file names like OR_ABI-L1b-RadF-M6C01_G16_s20193371110201_e20193371119509_c20193371119588-118900_0.nc doesn't work. There is a working pattern in satpy/etc/readers/abi_l1b.yaml for these files, but it satpy doesn't attempt with that after the first pattern fails.

To Reproduce

from satpy import Scene

fname = "OR_ABI-L1b-RadF-M6C01_G16_s20193371110201_e20193371119509_c20193371119588-118900_0.nc"
scn = Scene(filenames=[fname], reader='abi_l1b')

Expected behavior
The channel data would be read.

Actual results

[DEBUG: 2019-12-03 15:19:07 : satpy.readers.yaml_reader] Can't parse /home/lahtinep/data/satellite/geo/OR_ABI-L1b-RadF-M3C01_G16_s20182751200370_e20182751211137_c20182751211180-118900_0.nc with {system_environment:2s}_{mission_id:3s}-L1b-{observation_type:3s}{scene_abbr:s}-{scan_mode:2s}C01_{platform_shortname:3s}_s{start_time:%Y%j%H%M%S%f}_e{end_time:%Y%j%H%M%S%f}_c{creation_time:%Y%j%H%M%S%f}.nc{nc_version}.

Environment Info:

• OS: Linux
• Satpy Version: 0.18.2.dev7+gbf60e6aa (current master branch)

Additional context
If the reader config is overridden with $PPP_CONFIG_DIR/readers/abi_l1b.yaml with the first pattern removed, the reading works.

[pnuu]

Bah. The debug message above confused me, and there's no acknowledgement in the log that the scene creation actually worked. The reading actually works, the products were not created due to other problems.