I understand it's a test file, but need to decide how we want to handle it for release tooling purposes...
Description
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Reedy | T302893 Release MW 1.38.0 | |||
| Resolved | Reedy | T302912 Release 1.38.0-rc.0 | |||
| Resolved | Reedy | T306524 tests/phpunit/unit/includes/Settings/Source/fixtures/bad.json is an invalid JSON file |
Event Timeline
I'm guessing Scap doesn't handle this, nor does it specifically care unless you try and sync that file (or something higher in the test tree that includes this). It'll work fine when syncing all the things
Change 784680 had a related patch set uploaded (by Reedy; author: Reedy):
[mediawiki/tools/release@master] Skip 'bad.json'
Change 784680 merged by jenkins-bot:
[mediawiki/tools/release@master] make-release/scap_lint.py: Skip 'bad.json'
Can we rename the file so it doesn't have a .json extension? I think there is a reasonable expectation for things to be named *.json to actually be valid JSON.
bad.notjson
Was added in rMW9a4af2566438: Introduced settings sources and formats by @dduvall
You replied before I finished replying... I was going to ask if we had prescedent of doing that.
I'll stick up a patch to rename it; can revert the hack later
Change 784682 had a related patch set uploaded (by Reedy; author: Reedy):
[mediawiki/core@master] tests: Rename fixtures/bad.json
Change 784706 had a related patch set uploaded (by Reedy; author: Reedy):
[mediawiki/tools/release@master] Revert "make-release/scap_lint.py: Skip 'bad.json'"
Change 784682 merged by jenkins-bot:
[mediawiki/core@master] tests: Rename fixtures/bad.json
Change 784707 had a related patch set uploaded (by Reedy; author: Reedy):
[mediawiki/core@REL1_38] tests: Rename fixtures/bad.json
Change 784707 merged by jenkins-bot:
[mediawiki/core@REL1_38] tests: Rename fixtures/bad.json
Change 784706 merged by jenkins-bot:
[mediawiki/tools/release@master] Revert "make-release/scap_lint.py: Skip 'bad.json'"