| Summary: |
odd results of build-compare suggesting ram corruption on OBS machines |
| Product: |
[openSUSE] openSUSE.org
|
Reporter: |
Bruno Pitrus <brunopitrus> |
| Component: |
BuildService | Assignee: |
Olaf Hering <ohering> |
| Status: |
RESOLVED
INVALID
|
QA Contact: |
Adrian Schröter <adrian.schroeter> |
| Severity: |
Critical
|
|
|
| Priority: |
P5 - None
|
CC: |
brunopitrus
|
| Version: |
unspecified | |
|
| Target Milestone: |
--- | |
|
| Hardware: |
All | |
|
| OS: |
All | |
|
| Whiteboard: |
|
|
Found By:
|
---
|
Services Priority:
|
|
|---|
|
Business Priority:
|
|
Blocker:
|
---
|
|---|
|
Marketing QA Status:
|
---
|
IT Deployment:
|
---
|
|---|
While building devel:tools:ide:vscode/code i started getting reposts of non-reproducible builds. build-compare reports differences on several webpacked JS files. Due to the extremely long lines, one must view the build log without linewrap to make any sense of the diff. What made me suspicious is that one of the compared files is obviously invalid JavaScript. This is from Tumbleweed code-1.80.1-1.3.aarch64 build: - (…snip…) t.AbstractMessageReader=c,function(e){e.fromOptions=function(e){let t,n;const r=new Map;let o;const s=new Map; (…) + (…snip…) t.AbstractMessageReader=c,function(e){e.fromOptionw Map,this._pendingRequestHandlers=new Map,this._requestDisposables=new Map,this._progressHandlers=n Notice the “Optionw” in the second line, as if a wrong memory page got loaded. The string is NOT present in the downloaded RPM, which features the content as in the first line. I've observed this problem on both x86_64 and aarch64 machines.