Skip to main content

Browse the archive

Revision 86455a624bb05eb7503ccbe340dca973f5dea4c8 authored by Mike Pennisi on 29 June 2018, 23:46:14 UTC, committed by Ms2ger on 02 July 2018, 14:25:31 UTC 
[fetch] Do not return value from cleanup fns
 
Today, the return value of functions provided to the `Test#add_cleanup`
function has no effect on the behavior of the test runner. Despite this,
some existing tests have already been authored to return the `null`
value.

An upcoming feature addition to testharness.js will cause the return
value to influence test results [1]. To allow the new test harness
feature to land without introducing harness errors, refactor existing
tests to omit a return value.

[1] https://github.com/web-platform-tests/wpt/issues/6075
1 parent 27406c9
Raw File
.pyup.yml 
# search for requirement files
# default: True
# allowed: True, False
search: False

# Specify requirement files by hand, default is empty
# default: empty
# allowed: list
requirements:
 - tools/wptrunner/requirements_chrome_android.txt:
      update: all
      pin: True
 - tools/wptrunner/requirements_edge.txt:
      update: all
      pin: True
 - tools/wptrunner/requirements_opera.txt:
      update: all
      pin: True
 - tools/wptrunner/requirements_servo.txt:
      update: all
      pin: True
 - tools/wptrunner/requirements_safari.txt:
      update: all
      pin: True
 - tools/wptrunner/requirements_sauce.txt:
      update: all
      pin: True
 - tools/wptrunner/requirements_ie.txt:
      update: all
      pin: True
 - tools/wptrunner/requirements.txt:
      update: all
      pin: True
 - tools/wptrunner/requirements_firefox.txt:
      update: all
      pin: True
 - tools/wptrunner/requirements_chrome.txt:
      update: all
      pin: True
 - tools/wpt/requirements.txt:
      update: all
      pin: True
back to top