How to interpet linking WARNINGs from conda-build 3.28.x? #5106
Comments
|
We also hit this issue in conda-forge/pennylane-lightning-gpu-feedstock#14, my suspicion is that the changes made in the recent conda-build does not handle run-exports correctly (because it's how our package relies on for the run dependencies). |
kenodegard
added
type::bug
|
@jdblischak @leofang since it's just a printed warning and AFAIK doesn't change how the package is built it should be safe to ignore the message yes, the recent updates to to be corrected in #5108 |
|
Thanks for speedy fix, Ken! Just wanna add that to most feedstocks on conda-forge this warning is indeed benign, however some feedstocks do impose a strict rule (i.e. setting |
|
ah didn't know that was a thing, we may expedite a patch release then |
While I would like this addressed quickly since the WARNING messages are an unnecessary distraction (eg they have delayed at least 2 PRs that have been linked to this Issue), I have to note that these WARNINGs do not result in a hard error. I verified this empirically. I pushed a test commit that set |
|
Since moving to 3.28, I've noticed these new warning messages. For us, the warning lines can be > 8 million characters, so it has increased our build logs from a few mb up to > 400mb, making them almost unusable and clogging up our build servers. I will pin to 3.27 for now, and keep an eye on this issue. Thanks. |
|
Thanks, John. I thought all warnings would be converted to errors when |
@thomashampson thanks for reporting! I've been having a terrible time trying to copy-paste from the build logs to report this Issue. I thought it was a temporary Azure glitch, but now the long load times make sense since the build logs have ballooned in size |
|
The increased logs broke |
Temporary change will intentionally be overridden by the next re-render. There is an issue with conda-build=3.28 that inflates the log sizes which led Travis to abort the build. ref: conda/conda-build#5106 Signed-off-by: Marcel Bargull <[email protected]>
|
#5108 has been merged, patch release coming this week |
I am working on fixing the linking issues in the tiledb-feestock recipe (specifically PR conda-forge/tiledb-feedstock#225)
However, I just started getting some never before seen WARNING messages. I couldn't find them documented, nor could I find similar conda-forge recipes with these WARNINGs. They look like the following:
Essentially it lists multiple identical
PrefixRecords. This comes from the following source code:conda-build/conda_build/post.py
Lines 1217 to 1224 in 950278b
Which was recently refactored in #5041 and included in the 3.28.0 release (diff).
I did a test run where I pinned the conda-forge infrastructure to use conda-build 3.27.0. This reverted the WARNING messages to INFO, eg the libxml2 WARNING above is
So my questions are:
The text was updated successfully, but these errors were encountered: