-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[Build]: Can't get the test files for paddle #20069
Comments
similar problem happened in my device as well. I encountered code errors in relevant log output as follow:
the only modification I made is to initiate building paddle test
|
I also initiate the building paddle test setting. I can finish the build process, but still don't have the test files |
@AndSonder please, check your CMake output. In case if you observe warning like Even if you already installed all required and still observe warning (I got this case), specify Please, note that for the moment tests are skipped due python incompatibilities |
Thank you very much for your reply. I will try it according to your method. I have another question: Do I need to make relevant Settings like this pr? @vurusovs |
Hi @AndSonder
with newer PDPD version. Do you know what was changed in PDPD? |
In 2.5 version, PDPD gradually abandoned the previous Fluid architecture, which led to a change in the path of many apis. In the above cases, |
You should use lower version of paddle, because lots of apis have been or will be removed from fluid even fluid itself |
Maybe we can support paddle 2.5.1 on another pr. |
We cannot merge any PR to paddle FE, because we use python 3.11 in validation, which is supported only since paddle 2.5 |
You are right, I can help you to solve this problem. |
Re-opened until migration to paddle 2.5.1 is completed |
OpenVINO Version
2022.3.0
Operating System
Ubuntu 18.04 (LTS)
Hardware Architecture
x86 (64 bits)
Target Platform
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 40
On-line CPU(s) list: 0-39
Thread(s) per core: 2
Core(s) per socket: 10
Socket(s): 2
NUMA node(s): 2
Vendor ID: GenuineIntel
CPU family: 6
Model: 79
Model name: Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz
Stepping: 1
CPU MHz: 2599.968
CPU max MHz: 3400.0000
CPU min MHz: 1200.0000
BogoMIPS: 4800.19
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 25600K
NUMA node0 CPU(s): 0-9,20-29
NUMA node1 CPU(s): 10-19,30-39
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb invpcid_single intel_pt ssbd ibrs ibpb stibp kaiser tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdseed adx smap xsaveopt cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts md_clear flush_l1d
Build issue description
When I finish the build, I can't get test files for paddle.
Build scrip or step-by-step to reproduce
Relevant log output
Issue submission checklist
The text was updated successfully, but these errors were encountered: