Bug 204419
| Summary: | EWS is trying to run testmasm | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Paulo Matos <pmatos> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | aakash_jain |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Paulo Matos
testmasm should not be running for jsc-only 32 bits but it is.
See
https://ews-build.webkit.org/#/builders/26/builds/128/steps/8/logs/stdio
However, steps.py:964 has:
if platform == 'jsc-only' and remotesfile:
self.command.extend(['--no-testmasm', '--no-testair', '--no-testb3', '--no-testdfg', '--no-testapi', '--memory-limited'])
and during testing we saw the proper behaviour. Only in production, this is not working.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Aakash Jain
This was a temporary deployment issue (as I used ‘buildbot reconfig’ instead of ‘buildbot restart’ yesterday). This was fixed when I restarted buildbot today afternoon.
Paulo Matos
Thanks.