You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On current master (win64, linux64, win32) we get the following errors:
Error in testset inference_qa:
Test Failed at C:\buildbot\worker-tabularasa\tester_win64\build\share\julia\test\inference_qa.jl:85
Expression:isempty(remove_unlikely_methodinstances(atrisk_triggers(m, first.(mivulnerabilities_exported))))
Evaluated:isempty(Core.MethodInstance[MethodInstance forconvert(::Type{Nothing}, ::Any), MethodInstance forfieldcount(::Any), MethodInstance forconvert(::Type{Union{}}, ::Any)])
Error in testset inference_qa:
Test Failed at C:\buildbot\worker-tabularasa\tester_win64\build\share\julia\test\inference_qa.jl:85
Expression:isempty(remove_unlikely_methodinstances(atrisk_triggers(m, first.(mivulnerabilities_exported))))
Evaluated:isempty(Core.MethodInstance[MethodInstance forconvert(::Type{Nothing}, ::Any), MethodInstance forfieldcount(::Any), MethodInstance forconvert(::Type{Union{}}, ::Any)])
ERROR: LoadError: Test run finished with errors
in expression starting at C:\buildbot\worker-tabularasa\tester_win64\build\share\julia\test\runtests.jl:89
ERROR: A test has failed. Please submit a bug report (https://github.com/JuliaLang/julia/issues)
There's a mostly-fix in #38455 (something "regressed" between passing tests and the subsequent merging of #37193). But it doesn't fix the problem for Windows, unfortunately. Can you try the steps in #37193 (comment) and see what triggers the fieldcount(::Any) issue?
Activity
timholy commentedon Nov 16, 2020
There's a mostly-fix in #38455 (something "regressed" between passing tests and the subsequent merging of #37193). But it doesn't fix the problem for Windows, unfortunately. Can you try the steps in #37193 (comment) and see what triggers the
fieldcount(::Any)issue?dkarrasch commentedon Nov 16, 2020
I can't help with windows testing, unfortunately. I just took the error messages from the most recent commit to
master.