[Tutorials] Veto df103_NanoAODHiggsAnalysis on Mac 10.13 #5943
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Because of these errors (see e.g. https://bit.ly/31y2jSa): ``` Plugin dlopen(libXrdSecgsi-4.so, 256): image not found sec.protocol libXrdSecgsi-4.so Secsss: 0x30 cryptography load failed; Protocol not supported ```
|
Starting build on |
hageboeck
approved these changes
Jun 29, 2020
Member
hageboeck
left a comment
hageboeck
left a comment
There was a problem hiding this comment.
It will probably work out of the box. I will just need to rebase.
Contributor
Author
|
@phsft-bot build just on mac1013/default with flags -DCTEST_TEST_EXCLUDE_NONE=On |
|
Starting build on |
Contributor
Author
|
Besides the weird fact that mac10.13 vetoes "239/815 tutorials" while ROOT-performance-centos7-multicore vetoes "239/815", things seem ok |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because of these errors (see e.g. https://bit.ly/31y2jSa):
@hageboeck i'm not sure whether this interferes with #5938