An error occurred while fetching the assigned milestone of the selected merge_request.
Avoid KeyError in OutputAnalysisConfig during the second pass
It was reported by @adohnalo that if setting the containersOnlyForMC
option in the output block, a KeyError would be raised here complaining about duplicated keys in containers
and containersOnlyForMC
. This happens during the second pass of configuring the blocks, when self.containers
has been updated by self.containersOnlyForMC
here during the first pass.
The proposed fix here is to clear self.containersOnlyForMC
after self.containers
is updated during the first pass.
Merge request reports
Activity
Filter activity
Please register or sign in to reply