-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ArchiverDataPoller failing to parse documents #11168
Comments
@todor-ivanov I think we discussed about this issue last week and we agreed that you would be looking into it. |
Update: This is a problem when parsing some XML files and it seems to be a bug while creating the XML file from CMSSW itself. So we end up with one section without a module label (which should be
Double checking regarding a possible core bug with the XML file in: |
@amaltaro So, it was confirmed the CMSSW release used when we have this problem: that they incorporated starting In summary, we are not dealing with a bug in WMCore and there is a fix in CMSSW in later 12.x releases. So, how should we proceed? Do we request this PR to be added to |
Fixed by #11198 |
Impact of the bug
WMAgent
Describe the bug
It's still unclear to me whether it's a bug or something new coming from a CMSSW release(?) Looking into the ArchiveDataReporter component in the FNAL submit6 agent, I see this error/traceback over and over [1]
How to reproduce it
No clue
Expected behavior
Investigate if there is anything wrong with those FJR and either add a protection in WMAgent, or actually fix whatever problem that needs to be fixed with ArchiveDataReporter and how those FJR documents are converted to WMArchive ones.
Additional context and error message
[1]
The text was updated successfully, but these errors were encountered: