[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bug#48598: 28.0.50; buffer-naming collisions involving bouncers in E
From: |
Michael Albinus |
Subject: |
Re: bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC |
Date: |
Fri, 22 Apr 2022 10:54:24 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
"J.P." <jp@neverwas.me> writes:
Hi,
>> If this fixes the problem, pls push the patch. And change the files
>> under test/infra/ accordingly, please.
>
> Thanks, I'd be happy to do that.
>
> Although, in light of my observations above, if you think it might make
> more sense to solicit additional insights (possibly relating the two), I
> could open a new bug instead. Alternatively (or in addition to that), I
> could run a few pipelines with the flag set to -j4 for various targets,
> perhaps with and without this patch applied, just to refresh and maybe
> revise our current understanding. (Just a thought.)
Well, you have your own Emacs branch. Perhaps you apply there the
Makefile patch, and add -j4 to the respective make -C test calls in the
gitlab test jobs, and see what happens?
Well, maybe -j2 is more appropriate on emba, because it has two
processors with one core per processor:
--8<---------------cut here---------------start------------->8---
root@emba:~# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 2
NUMA node(s): 1
Vendor ID: AuthenticAMD
CPU family: 21
Model: 1
Model name: AMD Opteron 62xx class CPU
Stepping: 2
CPU MHz: 2100.024
BogoMIPS: 4200.04
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 64K
L1i cache: 64K
L2 cache: 512K
NUMA node0 CPU(s): 0,1
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt pdpe1gb lm
rep_good nopl extd_apicid tsc_known_freq pni pclmulqdq ssse3 cx16 sse4_1 sse4_2
x2apic popcnt aes xsave avx hypervisor lahf_lm cmp_legacy cr8_legacy abm sse4a
misalignsse 3dnowprefetch osvw xop fma4 vmmcall arat
--8<---------------cut here---------------end--------------->8---
Best regards, Michael.
- Re: bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, (continued)
- Re: bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, J.P., 2022/04/11
- Re: bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, Lars Ingebrigtsen, 2022/04/11
- Re: bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, Michael Albinus, 2022/04/12
- Re: bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, J.P., 2022/04/15
- Re: bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, Michael Albinus, 2022/04/15
- Re: bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, J.P., 2022/04/15
- Re: bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, Michael Albinus, 2022/04/17
- Re: bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, J.P., 2022/04/18
- Re: bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, Michael Albinus, 2022/04/18
- Re: bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, J.P., 2022/04/21
- Re: bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC,
Michael Albinus <=