-
Notifications
You must be signed in to change notification settings - Fork 183
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
update TBB to 2019_U1 #4415
update TBB to 2019_U1 #4415
Conversation
please test |
The tests are being triggered in jenkins. |
A new Pull Request was created by @smuzaffar (Malik Shahzad Muzaffar) for branch IB/CMSSW_10_4_X/gcc700. @cmsbuild, @smuzaffar, @gudrutis, @mrodozov can you please review it and eventually sign? Thanks. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@Dr15Jones , any objection on updating this for 10.4.X? |
+externals |
This pull request is fully signed and it will be integrated in one of the next IB/CMSSW_10_4_X/gcc700 IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
@smuzaffar they are all in L1T that looks not very reproducible, and whose code was further updated yesterday morning. Let's retry once more, although I would say there is no connection with this PR |
please test |
The tests are being triggered in jenkins. |
we should really consider 1) deciding that this is a known feature of current L1 code, so there is no need to recheck it again and again, and 2) get the experts to prioritize fixing it (perhaps by not merging requested PRs..)
… On Oct 12, 2018, at 9:27 AM, Fabio Cossutti ***@***.***> wrote:
@smuzaffar they are all in L1T that looks not very reproducible, and whose code was further updated yesterday morning. Let's retry once more, although I would say there is no connection with this PR
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I have already urged them to look into this, I agree that this needs to become a priority |
yes, I agree - its a many months old problem...probably now means irreproducibility in production releases
… On Oct 12, 2018, at 9:35 AM, Fabio Cossutti ***@***.***> wrote:
I have already urged them to look into this, I agree that this needs to become a priority
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Yes, please do the update. |
@Dr15Jones I will let finish the test, and schedule the merge for next IB this evening |
-1 Tested at: 20c3f5a You can see the results of the tests here: I found follow errors while testing this PR Failed tests: UnitTests
I found errors in the following unit tests: ---> test testNumba had ERRORS |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 the unit test failure has been observed in the IB as well and looks independent on this PR. DQM changes seem also unrelated. |
merge |
New version 2019_U1 of TBB is available now.