Closed bearzx closed 2 years ago
@bearzx has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.
For some reason, glog needs to be on 0.4.0 version (latest 0..5.0) to make the testing part work (even it's just a simple import), otherwise some symbol not found error will arise.
cc @kgpai . Wondering if this has been known from other Velox users?
@bearzx has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.
@wenleix we explicitly depend on glog v 0.4.0 . I havent upgraded to 0.5.0 to see if they are compatible, but based on error it probably isnt.
@wenleix we explicitly depend on glog v 0.4.0 . I havent upgraded to 0.5.0 to see if they are compatible, but based on error it probably isnt.
Yeah building itself seems to be fine, but when testing it'll need glog to be on 0.4.0 as 0.5.0 removed some non-public symbols, which caused errors. Here's a discussion for this issue that I found: https://trac.macports.org/ticket/62921
@bearzx has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.
@bearzx has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.
In this PR I'm added a new Github workflow to enable nightly build for conda. But right now for developing and testing, I left the trigger as new PR comes in, so it's not really "nightly build" yet.
Multiple points to note:
torcharrow
, so the failing tests will have messages like "torcharrow.test" != "test". I'll leave this to further investigation and depending on whether we really want to run unittests in conda build workflows, we may end up not bothering with it.This PR finishes the building part, but I still need to upload the built artifact to conda, which I'll leave as a todo.