test262.properties format inconsistency after test262 submodule updates

[anivar]

Problem

After updating the test262 submodule, the test runner generates different formats of test262.properties depending on the update flags used. This causes CI failures because the test runner expects {unsupported: [...]} markers to identify tests that should be skipped due to unsupported features.

Available Generation Options

Current Options for -DupdateTest262properties=

• all: Enables rollup + stats + unsupported markers (what CI currently expects)
  • Generates: Statistics like 58/241 (24.07%), rollup sections, {unsupported: [...]} markers
• none: Disables all features (rollup, stats, unsupported)
  • Generates: Clean list without any statistics or markers
• ~all: Inverts 'all', same as 'none'
  • Generates: Clean list without any statistics or markers
• true or empty string: Enables all features by default (same as 'all')
• rollup: Enables only rollup sections
• stats: Enables only statistics
• unsupported: Enables only unsupported markers
• Combinations: Can use comma-separated values like rollup,unsupported

Current Behavior

• CI expects the format generated by =all (with statistics and unsupported markers)
• Using =~all or =none generates a cleaner format but causes CI failures
• The test runner LINE_SPLITTER regex still expects to parse {unsupported: [...]} format

Expected Behavior

Either:

1. The test runner should be updated to work without the unsupported markers, OR
2. The generation should consistently include unsupported markers regardless of test262 version, OR
3. CI should be updated to handle the new clean format

Steps to Reproduce

1. Update test262 submodule to latest
2. Run: ./gradlew :tests:test --tests Test262SuiteTest --rerun-tasks -DupdateTest262properties=~all
3. Note the generated test262.properties lacks {unsupported: [...]} markers
4. CI fails trying to run tests that require unsupported features

Environment

• Latest test262 submodule (commit 3fd4ec27f1)
• Rhino master branch
• Test262SuiteTest.java lines 118-135 contain the flag parsing logic

Workaround

Currently using -DupdateTest262properties=all to generate the format with unsupported markers that CI expects.

[aardvark179]

Yes, this is a way you can break CI, but the options are also useful for quickly determining if unsupported features are really still unsupported.