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

Non-reproducibility in 29634.911 #45505

Open
makortel opened this issue Jul 18, 2024 · 10 comments
Open

Non-reproducibility in 29634.911 #45505

makortel opened this issue Jul 18, 2024 · 10 comments

Comments

@makortel
Copy link
Contributor

The comparisons of workflow 29634.911 show differences randomly.

@makortel
Copy link
Contributor Author

assign geometry, upgrade

@cmsbuild
Copy link
Contributor

New categories assigned: geometry,upgrade

@Dr15Jones,@civanch,@bsunanda,@makortel,@mdhildreth,@srimanob,@subirsarkar you have been requested to review this Pull request/Issue and eventually sign? Thanks

@cmsbuild
Copy link
Contributor

cms-bot internal usage

@cmsbuild
Copy link
Contributor

A new Issue was created by @makortel.

@Dr15Jones, @antoniovilela, @makortel, @mandrenguyen, @rappoccio, @sextonkennedy, @smuzaffar can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

@makortel
Copy link
Contributor Author

The non-reproducibility is present even after #45442 was merged, I noticed it in #45443 (comment)

@srimanob
Copy link
Contributor

srimanob commented Aug 1, 2024

After adding 24834.911 back to the PR test, I see that 24834.911 seems to be stable. In addition, the issues seems to show up only in Tracking, EGamma, BTag, so it seems to me that it relates to geometry, and the issue just comes to the surface when we fix HGCal initialization, and rule out the issue from HGCal failure in PR test.

Issue may come from Tracker part which is also changed between D98 and D110.

@perrotta
Copy link
Contributor

Also observed in #45699

@mmusich
Copy link
Contributor

mmusich commented Nov 25, 2024

Recently I've been seeing non-reproducibility in HLT trigger results in workflow 29634.911 and 29634.911 alone.
Recent examples:

The reproducibility issue is always of the type:

Found 10 matching events, out of which 1 have different HLT results

      Events    Accepted      Gained        Lost       Other  Trigger
          10           4          +1           -           -  pPuppiHT450
          10           3          +1           -           -  pSinglePuppiJet230
          10           0           -           -          ~1  HLT_AK4PFPuppiJet520
          10           0           -           -          ~1  HLT_PFPuppiHT1070
Created the following JSON files:
 /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/upload/triggerResults/29634.911_TTbar_14TeV+Run4D110_DD4hep/HLT.json   

did we change anything recently in the L1T puppi jet seeding algorithm in cmssw ? @cms-sw/l1-l2

@smuzaffar
Copy link
Contributor

@mmusich , today we have enabled the usage of AuthenticAMD nodes for PR/baseline relval comparison (#46669) . Test AuthenticAMD via cms-sw/cms-bot#2374 did show this non-reproducibility 1 out of 7 times

@mmusich
Copy link
Contributor

mmusich commented Nov 25, 2024

today we have enabled the usage of AuthenticAMD nodes for PR/baseline relval comparison [...] did show this non-reproducibility 1 out of 7 times

thanks, the question to L1 stands.

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