See https://treeherder.mozilla.org/#/jobs?repo=try&revision=f6606b00b618c478f6008ae297af3d1c91bf500f

Here's the failure tests:
(a) Remote process setup
netwerk/test/unit_ipc/*

(b) Require nodejs (that means we don't have H2 tests on Fenix)
test_immutable.js
test_origin.js
test_anonymous-coalescing.js
test_socks.js
test_http2.js
test_altsvc.js
test_header_Server_Timing.js
test_trr.js
test_captive_portal_service.js
test_esni_dns_fetch.js

(c) DNSv6 issues
test_network_connectivity_service.js

(d) Others
netwerk/test/unit/test_redirect-caching_failure.js
netwerk/test/unit/test_redirect_failure.js

This should be turned to a meta and broken down for each particular group/test.

I could take a look at the (d) group, I wrote those.

P2, feel free to escalate if this blocks anything.

Currently, to run xpcshell tests on Fenix you do either of:

1. ./mach try chooser with android-7.0x86-64 xpcshell filter and running all the filtered tests
2. manually trigger xpcshell tests on an empty push with xpcshell android filter

m-c and try is no longer running tests for Fennec as it's ESR68 based only now.

I rebased and rerun the patch series Junior used to report this bug originally (it was no longer available) and here is the result:

I see 3 types of failures here:

1. PERMA FAIL ON ANDROID (known before, disabled in bug 865006)
   TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_socks.js | xpcshell return code: 0

2. MISSING NODE/H2 SERVER
   TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_immutable.js | xpcshell return code: 0
   TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_immutable.js | run_test - [run_test : 13] "" != ""
   TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_origin.js | xpcshell return code: 0
   TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_origin.js | run_test - [run_test : 14] "" != ""
   TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_anonymous-coalescing.js | xpcshell return code: 0
   TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_anonymous-coalescing.js | run_test - [run_test : 20] "" != ""
   TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_http2.js | xpcshell return code: 0
   TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_http2.js | testOnStopRequest - [testOnStopRequest : 84] false == true
   TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_altsvc.js | xpcshell return code: 0
   TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_altsvc.js | run_test - [run_test : 31] "" != ""
   TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_header_Server_Timing.js | xpcshell return code: 0
   TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_trr.js | xpcshell return code: 0
   TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_trr.js | setup - [setup : 36] "" != ""
   TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_captive_portal_service.js | xpcshell return code: 0
   TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_captive_portal_service.js | test_redirect_https - [test_redirect_https : 189] "" != ""
   TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_esni_dns_fetch.js | xpcshell return code: 0
   TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_esni_dns_fetch.js | setup - [setup : 27] "" != ""

3. NULL DEREF: missing sJavaVM in Utils.js!GetEnvForThread: https://searchfox.org/mozilla-central/rev/be7d1f2d52dd9474ca2df145190a817614c924e4/widget/android/jni/Utils.cpp#169, we are probably missing a call to https://searchfox.org/mozilla-central/rev/be7d1f2d52dd9474ca2df145190a817614c924e4/mozglue/android/APKOpen.cpp#295
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_bug528292_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_cookie_header_stripped.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_cacheflags_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_cache-entry-id_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_cache_jar_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_channel_close_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_cookiejars_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_dns_cancel_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_dns_service_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_duplicate_headers_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_event_sink_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_head_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_headers_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_httpsuspend_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_post_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_predictor_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_progress_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_redirect-caching_canceled_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_redirect-caching_failure_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_redirect-caching_passing_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_redirect_canceled_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_redirect_failure_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_redirect_passing_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_redirect_different-protocol_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_reentrancy_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_resumable_channel_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_simple_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_synthesized_response_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_xmlhttprequest_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_XHR_redirects.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_redirect_history_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_reply_without_content_type_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_getHost_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_alt-data_simple_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_alt-data_stream_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_alt-data_closeWithStatus_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_original_sent_received_head_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_channel_id.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_trackingProtection_annotateChannels_wrap1.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_trackingProtection_annotateChannels_wrap2.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_channel_priority_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_multipart_streamconv_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_alt-data_cross_process_wrap.js | xpcshell return code: 139
   TEST-UNEXPECTED-FAIL | netwerk/test/unit_ipc/test_httpcancel_wrap.js | xpcshell return code: 139

• test_socks failure is an old issue, not sure about a priority here (probably low)
• missing node or the server start failure is an infra failure (will file a separate bug)
• the null sJavaVM is something I don't understand either and will file a separate bug for this too

New push after enabling node on android:
https://treeherder.mozilla.org/#/jobs?repo=try&collapsedPushes=511147%2C509985%2C511151&searchStr=xpcshell%2Candroid%2C&revision=1473424aef5d1f3547927197f51c2b6e65790198

(In reply to Honza Bambas (:mayhemer) from comment #4)

New push after enabling node on android:
https://treeherder.mozilla.org/#/jobs?repo=try&collapsedPushes=511147%2C509985%2C511151&searchStr=xpcshell%2Candroid%2C&revision=1473424aef5d1f3547927197f51c2b6e65790198

Node works now!

New push to check which tests are still failing after few bugs have been fixed:
https://treeherder.mozilla.org/#/jobs?repo=try&collapsedPushes=511147%2C509985%2C511151%2C636183%2C632551%2C632394%2C631064%2C631042%2C627952%2C627807&searchStr=android%2Cxpc&revision=96313f656fc766bc7b4273bdf56a0d67bad1c760

I will create a patch to enable those that work now in a new bug, so that we have a better coverage.

Android tests work now.