Bug 176361 - REGRESSION(r221601/221602/221607?): It broke all JSC tests on ARMv7 traditional platform
Summary: REGRESSION(r221601/221602/221607?): It broke all JSC tests on ARMv7 tradition...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P1 Blocker
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-05 04:50 PDT by Csaba Osztrogonác
Modified: 2017-09-05 07:43 PDT (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Csaba Osztrogonác 2017-09-05 04:50:14 PDT
before:
- r221599
- https://build.webkit.org/builders/JSCOnly%20Linux%20ARMv7%20Traditional%20Release/builds/1360
- 46 failures

after:
- r221607
- https://build.webkit.org/builders/JSCOnly%20Linux%20ARMv7%20Traditional%20Release/builds/1361
- 25034 failures

JSC changes in this interval:
- https://trac.webkit.org/changeset/221607/webkit (Saam, r=Keith)
- https://trac.webkit.org/changeset/221602/webkit (Saam, r=Filip)
- https://trac.webkit.org/changeset/221601/webkit (Yusuke, r=Keith)

I don't have any time and any interest to debug or fix this issue,
I just reported because I noticed it on the buildbot, maybe anyone
else is interested in fixing an ARMv7 bug (with the traditional
assembler which emits ARM instrucionts instead of Thumbs). Maybe
Caio or someone else from Igalia is interested in it, because I'm
pretty sure that the ARMv6 backend is affected too.

I can help you only a little bit, I can trigger force builds 
on the bot to be able to determine which change is the culprit
from the above 3 JSC chages.
Comment 1 Csaba Osztrogonác 2017-09-05 04:52:13 PDT
clean build on r221601: (in progress)
- https://build.webkit.org/builders/JSCOnly%20Linux%20ARMv7%20Traditional%20Release/builds/1364
Comment 2 Caio Lima 2017-09-05 05:40:59 PDT
I will take a look on that.
Comment 3 Caio Lima 2017-09-05 05:43:21 PDT
(In reply to Csaba Osztrogonác from comment #0)
> 
> I can help you only a little bit, I can trigger force builds 
> on the bot to be able to determine which change is the culprit
> from the above 3 JSC chages.

Please, it would be great. BTW, Thanks for the report.
Comment 4 Csaba Osztrogonác 2017-09-05 05:50:20 PDT
(In reply to Csaba Osztrogonác from comment #1)
> clean build on r221601: (in progress)
> -
> https://build.webkit.org/builders/
> JSCOnly%20Linux%20ARMv7%20Traditional%20Release/builds/1364

It seems good, let's see r221602:
https://build.webkit.org/builders/JSCOnly%20Linux%20ARMv7%20Traditional%20Release/builds/1365
Comment 5 Csaba Osztrogonác 2017-09-05 05:51:44 PDT
sorry, wrong link, r221602 is here:
https://build.webkit.org/builders/JSCOnly%20Linux%20ARMv7%20Traditional%20Release/builds/1366
Comment 6 Csaba Osztrogonác 2017-09-05 07:43:13 PDT
Very strange, after a clean build everything works fine on r221607 too:
https://build.webkit.org/builders/JSCOnly%20Linux%20ARMv7%20Traditional%20Release/builds/1367

It's strange, because ARMv7 Thumbs and AArch64 bots have exactly same build
system and don't have this issue, so I didn't expect an incremental build 
issue. But it seems it was.

Sorry for the noise.