Skip to content
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

[AARCH64] Unit test DQM/HLTEvF/testTriggerMonitors fails with FileOpenError #40904

Closed
iarspider opened this issue Mar 1, 2023 · 10 comments
Closed

Comments

@iarspider
Copy link
Contributor

Log file: link

Error message:

%MSG
----- Begin Fatal Exception 01-Mar-2023 03:54:42 CET-----------------------
An exception of category 'FileOpenError' occurred while
   [0] Calling InputSource::readFile_
   [1] Opening DQM Root file
Exception Message:

Input file file:DQMIO.root was not found, could not be opened, or is corrupted.
   Additional Info:
      [a] Fatal Root Error: @SUB=TStorageFactoryFile::Init
file DQMIO.root probably not closed, trying to recover

----- End Fatal Exception -------------------------------------------------

Failure running testTriggerMonitors_harvesting_cfg.py: status 84

---> test testTriggerMonitors had ERRORS
@iarspider
Copy link
Contributor Author

assign dqm

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 1, 2023

New categories assigned: dqm

@micsucmed,@rvenditti,@emanueleusai,@syuvivida,@pmandrik you have been requested to review this Pull request/Issue and eventually sign? Thanks

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 1, 2023

A new Issue was created by @iarspider .

@Dr15Jones, @perrotta, @dpiparo, @rappoccio, @makortel, @smuzaffar can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

@Dr15Jones
Copy link
Contributor

@iarspider @smuzaffar
It looks like several tests write a file named DQMIO.root. When running the tests, where do these files actually appear? It is possible that another tests was in the process of writing a DQMIO.root file while the test that failed is trying to read it.

@smuzaffar
Copy link
Contributor

@Dr15Jones , by default all the files are generated in top level CMSSW_BASE directory ( unless unit test creates it own sub directory). There is good chance that multiple tests might be writing same output file and as arm nodes has a lot of CPUs so there is more chance of hit such issues for aarch64

@Dr15Jones
Copy link
Contributor

The test DQMOffline/Trigger/test/testHLTFiltersDQMonitor_cfg.py also writes a DQMIO.root file.

@smuzaffar
Copy link
Contributor

I am running now all the unit tests (in serial mode) to see what type of files each test generate :-)

@missirol
Copy link
Contributor

missirol commented Mar 2, 2023

The test DQMOffline/Trigger/test/testHLTFiltersDQMonitor_cfg.py also writes a DQMIO.root file.

I think that's caused by some unit tests I introduced (#40334, #40426), my bad. I tried to fix this in #40928. Thanks for finding the issue, @Dr15Jones.

@perrotta
Copy link
Contributor

@iarspider I think this issue can get closed now: isn't it?

@iarspider
Copy link
Contributor Author

@perrotta I agree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants