Skip to content
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.

Sign up for GitHub

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

Jump to bottom

ci: fix wsl2 lsmem: This system does not support memory blocks #556

Closed
petermetz opened this issue Feb 8, 2021 · 0 comments · Fixed by #723
Closed

ci: fix wsl2 lsmem: This system does not support memory blocks #556

petermetz opened this issue Feb 8, 2021 · 0 comments · Fixed by #723
Assignees
@petermetz
Labels
bug Something isn't working good-first-issue Good for newcomers Hacktoberfest Hacktoberfest participants are welcome to take a stab at issues marked with this label.
Milestone
v0.4.0

Comments

@petermetz
Copy link
Contributor

Describe the bug

On WSL2 the ./tools/ci.sh script fails.

To Reproduce

  1. Clone the project onto a WSL 2 Ubuntu 20.04 LTS installation
  2. Run ./tools/ci.sh

Expected behavior

CI to not fail

Logs/Stack traces

5.0.17(1)-release
++ command -v lscpu
+ '[' -x /usr/bin/lscpu ']'
+ lscpu
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   39 bits physical, 48 bits virtual
CPU(s):                          12
On-line CPU(s) list:             0-11
Thread(s) per core:              2
Core(s) per socket:              6
Socket(s):                       1
Vendor ID:                       GenuineIntel
CPU family:                      6
Model:                           158
Model name:                      Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz
Stepping:                        10
CPU MHz:                         2592.009
BogoMIPS:                        5184.01
Hypervisor vendor:               Microsoft
Virtualization type:             full
L1d cache:                       192 KiB
L1i cache:                       192 KiB
L2 cache:                        1.5 MiB
L3 cache:                        9 MiB
Vulnerability Itlb multihit:     KVM: Vulnerable
Vulnerability L1tf:              Mitigation; PTE Inversion
Vulnerability Mds:               Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown
Vulnerability Meltdown:          Mitigation; PTI
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling
Vulnerability Srbds:             Unknown: Dependent on hypervisor status
Vulnerability Tsx async abort:   Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology cpuid pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti ssbd ibrs ibpb stibp fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves flush_l1d arch_capabilities
++ command -v lsmem
+ '[' -x /usr/bin/lsmem ']'
+ lsmem
lsmem: This system does not support memory blocks
2021-02-06T22:18:11-0800 [CI] FAILURE - runtime=0 seconds.

Screenshots

N/A

Cloud provider or hardware configuration:

Development machine, WSL 2

Operating system name, version, build:

Windows 10, WSL2 -> Ubuntu 20.04 LTS

Hyperledger Cactus release version or commit (git rev-parse --short HEAD):

04ea8bb

Hyperledger Cactus Plugins/Connectors Used

N/A

Additional context

N/A

cc: @takeutak @sfuji822 @hartm @jonathan-m-hamilton @AzaharaC @jordigiam @kikoncuo
@petermetz petermetz added bug Something isn't working good-first-issue Good for newcomers Hacktoberfest Hacktoberfest participants are welcome to take a stab at issues marked with this label. labels Feb 8, 2021
@petermetz petermetz added this to the v0.5.0 milestone Feb 8, 2021
petermetz added a commit to petermetz/cacti that referenced this issue Mar 24, 2021
@petermetz
fix(tools): ci.sh wsl2 lsmem does not support memory blocks hyperledg…
95a2d99 
…er-cacti#556

Added a fallback || true suffix to the lsmem, lscpu and smem commands
which are used by the ci.sh script to dump diagnostic information about
the hardware of the CI runner prior to actually proceeding with the
execution of the full build+test suite.

The existing guards examining the presence of the lsmem binary were
not enough because the lsmem binary is indeed present on WSL 2
Ubuntu, it just does not work as intended (exit code is non-zero which
crashes the ci.sh script by design)

Fixes hyperledger-cacti#556

Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz added a commit to petermetz/cacti that referenced this issue Mar 25, 2021
@petermetz
fix(tools): ci.sh wsl2 lsmem does not support memory blocks hyperledg…
74f2c04 
…er-cacti#556

Added a fallback || true suffix to the lsmem, lscpu and smem commands
which are used by the ci.sh script to dump diagnostic information about
the hardware of the CI runner prior to actually proceeding with the
execution of the full build+test suite.

The existing guards examining the presence of the lsmem binary were
not enough because the lsmem binary is indeed present on WSL 2
Ubuntu, it just does not work as intended (exit code is non-zero which
crashes the ci.sh script by design)

Fixes hyperledger-cacti#556

Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
@petermetz petermetz mentioned this issue Mar 25, 2021
Merged
@petermetz petermetz modified the milestones: v0.5.0, v0.4.0 Mar 25, 2021
@petermetz petermetz self-assigned this Mar 25, 2021
petermetz added a commit to petermetz/cacti that referenced this issue Mar 26, 2021
@petermetz
fix(tools): ci.sh wsl2 lsmem does not support memory blocks hyperledg…
75565de 
…er-cacti#556

Added a fallback || true suffix to the lsmem, lscpu and smem commands
which are used by the ci.sh script to dump diagnostic information about
the hardware of the CI runner prior to actually proceeding with the
execution of the full build+test suite.

The existing guards examining the presence of the lsmem binary were
not enough because the lsmem binary is indeed present on WSL 2
Ubuntu, it just does not work as intended (exit code is non-zero which
crashes the ci.sh script by design)

Fixes hyperledger-cacti#556

Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz added a commit to petermetz/cacti that referenced this issue Mar 30, 2021
@petermetz
fix(tools): ci.sh wsl2 lsmem does not support memory blocks hyperledg…
8de98b9 
…er-cacti#556

Added a fallback || true suffix to the lsmem, lscpu and smem commands
which are used by the ci.sh script to dump diagnostic information about
the hardware of the CI runner prior to actually proceeding with the
execution of the full build+test suite.

The existing guards examining the presence of the lsmem binary were
not enough because the lsmem binary is indeed present on WSL 2
Ubuntu, it just does not work as intended (exit code is non-zero which
crashes the ci.sh script by design)

Fixes hyperledger-cacti#556

Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz added a commit that referenced this issue Mar 30, 2021
@petermetz
fix(tools): ci.sh wsl2 lsmem does not support memory blocks #556
24f8c25 
Added a fallback || true suffix to the lsmem, lscpu and smem commands
which are used by the ci.sh script to dump diagnostic information about
the hardware of the CI runner prior to actually proceeding with the
execution of the full build+test suite.

The existing guards examining the presence of the lsmem binary were
not enough because the lsmem binary is indeed present on WSL 2
Ubuntu, it just does not work as intended (exit code is non-zero which
crashes the ci.sh script by design)

Fixes #556

Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
jordigiam pushed a commit to kikoncuo/cactus that referenced this issue Apr 8, 2021
@petermetz
fix(tools): ci.sh wsl2 lsmem does not support memory blocks hyperledg…
d6e6e62 
…er-cacti#556

Added a fallback || true suffix to the lsmem, lscpu and smem commands
which are used by the ci.sh script to dump diagnostic information about
the hardware of the CI runner prior to actually proceeding with the
execution of the full build+test suite.

The existing guards examining the presence of the lsmem binary were
not enough because the lsmem binary is indeed present on WSL 2
Ubuntu, it just does not work as intended (exit code is non-zero which
crashes the ci.sh script by design)

Fixes hyperledger-cacti#556

Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@petermetz petermetz

Labels
bug Something isn't working good-first-issue Good for newcomers Hacktoberfest Hacktoberfest participants are welcome to take a stab at issues marked with this label.
Projects
None yet
Milestone
v0.4.0
Development

Successfully merging a pull request may close this issue.

fix(tools): ci.sh wsl2 lsmem does not support memory blocks #556 petermetz/cacti
1 participant
@petermetz