Modified: trunk/Tools/BuildSlaveSupport/ews-app/ews/views/statusbubble.py (252938 => 252939)
--- trunk/Tools/BuildSlaveSupport/ews-app/ews/views/statusbubble.py 2019-11-29 11:11:00 UTC (rev 252938)
+++ trunk/Tools/BuildSlaveSupport/ews-app/ews/views/statusbubble.py 2019-11-29 13:17:27 UTC (rev 252939)
@@ -40,7 +40,7 @@
# These queue names are from shortname in https://trac.webkit.org/browser/webkit/trunk/Tools/BuildSlaveSupport/ews-build/config.json
# FIXME: Auto-generate this list https://bugs.webkit.org/show_bug.cgi?id=195640
ALL_QUEUES = ['style', 'ios', 'ios-sim', 'mac', 'mac-debug', 'gtk', 'wpe', 'wincairo', 'win',
- 'ios-wk2', 'mac-wk1', 'mac-wk2', 'mac-debug-wk1', 'api-ios', 'api-mac', 'bindings', 'jsc', 'jsc-armv7', 'jsc-mips', 'webkitperl', 'webkitpy', 'services']
+ 'ios-wk2', 'mac-wk1', 'mac-wk2', 'mac-debug-wk1', 'api-ios', 'api-mac', 'bindings', 'jsc', 'jsc-armv7', 'jsc-mips', 'jsc-i386', 'webkitperl', 'webkitpy', 'services']
# FIXME: Auto-generate the queue's trigger relationship
QUEUE_TRIGGERS = {
'api-ios': 'ios-sim',
Modified: trunk/Tools/ChangeLog (252938 => 252939)
--- trunk/Tools/ChangeLog 2019-11-29 11:11:00 UTC (rev 252938)
+++ trunk/Tools/ChangeLog 2019-11-29 13:17:27 UTC (rev 252939)
@@ -1,3 +1,14 @@
+2019-11-29 Paulo Matos <pma...@igalia.com>
+
+ Move jsc-i386 from old to new EWS
+ https://bugs.webkit.org/show_bug.cgi?id=204667
+
+ Reviewed by Aakash Jain.
+
+ * BuildSlaveSupport/ews-app/ews/views/statusbubble.py:
+ (StatusBubble):
+ * QueueStatusServer/config/queues.py:
+
2019-11-28 Fujii Hironori <hironori.fu...@sony.com>
Remove ENABLE_KEYBOARD_CODE_ATTRIBUTE and ENABLE_KEYBOARD_KEY_ATTRIBUTE macros
Modified: trunk/Tools/QueueStatusServer/config/queues.py (252938 => 252939)
--- trunk/Tools/QueueStatusServer/config/queues.py 2019-11-29 11:11:00 UTC (rev 252938)
+++ trunk/Tools/QueueStatusServer/config/queues.py 2019-11-29 13:17:27 UTC (rev 252939)
@@ -32,7 +32,6 @@
# Eventually the list of queues may be stored in the data store.
all_queue_names = [
"commit-queue",
- "jsc-i386-ews",
]
# If the patch is still active after this much time, then a bot must have frozen or rebooted,