starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

TabTests.cpp test cases fail to run - TAEF harness fails to run with "[HRESULT: 0x80270254] Failed to create the test host process for out of process test execution" #3474

New Issue
Closed
opened 2026-01-30 23:22:10 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 23:22:10 +00:00
Owner
Copy Link

Originally created by @metathinker on GitHub (Aug 19, 2019).

Originally assigned to: @zadjii-msft on GitHub.

On my computer, the test case file src\cascadia\LocalTests_TerminalApp\TabTests.cpp fails to run test setup with the above error message. I'm not sure if this is a general problem or just in my setup, but these tests don't seem to run in Azure DevOps CI (I checked test run 31597) so I can't be sure.

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.295]
Windows Terminal version: current master commit 734fc1dcc6

Steps to reproduce

  1. Checkout the Terminal repo.
  2. Run tools\razzle.cmd & bz rel to get a successful build.
  3. Run: "%TAEF%" bin\%PLATFORM%\Release\LocalTests_TerminalApp\TerminalApp.LocalTests.dll /name:"TerminalAppLocalTests::TabTests::*"

Expected behavior

All tests pass.

Actual behavior

The test file does not run at all, with error 0x80270254 == E_APPLICATION_NOT_REGISTERED (lines manually wrapped):

X:\> "%TAEF%"
  bin\x64\Release\LocalTests_TerminalApp\TerminalApp.LocalTests.dll
  /name:"TerminalAppLocalTests::TabTests::*"

Test Authoring and Execution Framework v10.38k for x64
TAEF: Deploying custom AppXManifest...
  Copying X:\bin\x64\Release\LocalTests_TerminalApp\TerminalApp.LocalTests.AppxManifest.xml
  to X:\bin\x64\Release\LocalTests_TerminalApp\AppXManifest.xml
Warning: TAEF: Using TE.ProcessHost.exe as the Application Executable for UAP tests
  is deprecated, please consider using TE.ProcessHost.UAP.exe in your custom manifest.
Error: TAEF: [HRESULT: 0x80270254] Failed to create the test host process for
  out of process test execution. (The IApplicationActivationManager::
  ActivateApplication call failed while using a default host. TAEF's ETW logs
  which are gathered with the /enableEtwLogging switch should contain
  events from relevant providers that may help to diagnose the failure.)

StartGroup: TerminalAppLocalTests::TabTests::TryInitXamlIslands
EndGroup: TerminalAppLocalTests::TabTests::TryInitXamlIslands [Blocked]

StartGroup: TerminalAppLocalTests::TabTests::TryCreateLocalWinRTType
EndGroup: TerminalAppLocalTests::TabTests::TryCreateLocalWinRTType [Blocked]

StartGroup: TerminalAppLocalTests::TabTests::TryCreateXamlObjects
EndGroup: TerminalAppLocalTests::TabTests::TryCreateXamlObjects [Blocked]

StartGroup: TerminalAppLocalTests::TabTests::TryCreateTab
EndGroup: TerminalAppLocalTests::TabTests::TryCreateTab [Blocked]

Summary of TAEF Warnings:
    Warning: TAEF: Using TE.ProcessHost.exe as the Application Executable for UAP tests
      is deprecated, please consider using TE.ProcessHost.UAP.exe in your custom manifest.

Summary of Errors Outside of Tests:
    Error: TAEF: [HRESULT: 0x80270254] Failed to create the test host process for
      out of process test execution. (The IApplicationActivationManager::
      ActivateApplication call failed while using a default host. TAEF's ETW logs
      which are gathered with the /enableEtwLogging switch should contain
      events from relevant providers that may help to diagnose the failure.)

Summary of Non-passing Tests:
    TerminalAppLocalTests::TabTests::TryInitXamlIslands [Blocked]
    TerminalAppLocalTests::TabTests::TryCreateLocalWinRTType [Blocked]
    TerminalAppLocalTests::TabTests::TryCreateXamlObjects [Blocked]
    TerminalAppLocalTests::TabTests::TryCreateTab [Blocked]

Summary: Total=4, Passed=0, Failed=0, Blocked=4, Not Run=0, Skipped=0

Creating the ETW log and parsing it with Windows' built-in tracerpt.exe tool yields a number of interesting errors. As best as I can tell from my very limited knowledge, there was a problem with the AppX package extensions (<Extension> elements in AppXManifest.xml).

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="CombaseTraceLoggingProvider" Guid="{1aff6089-e863-4d36-bdfd-3581f07440be}" />
    <EventID>0</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x0</Keywords>
    <TimeCreated SystemTime="2019-08-18T22:19:27.701635500-07:00" />
    <Execution ProcessID="8272" ThreadID="11028" ProcessorID="0" KernelTime="315" UserTime="405" />
    <Channel />
    <Computer />
  </System>
  <EventData>
    <!-- Michael: This is 0x80040154 == REGDB_E_CLASSNOTREG
         "Class not registered" -->
    <Data Name="hresult">-2147221164</Data>
    <Data Name="code"></Data>
    <Data Name="message"></Data>
    <Data Name="function"></Data>
    <Data Name="fileName">onecore\com\combase\extensioncatalog\extensioncatalog.cpp</Data>
    <Data Name="lineNumber">    1215</Data>
  </EventData>
  <RenderingInfo Culture="en-US">
    <Task>ComError</Task>
  </RenderingInfo>
</Event>

[snip snip]

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ActivationManager" Guid="{cf7f94b3-08dc-5257-422f-497d7dc86ab3}" />
    <EventID>0</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x0</Keywords>
    <TimeCreated SystemTime="2019-08-18T22:19:27.702335700-07:00" />
    <Execution ProcessID="8272" ThreadID="11028" ProcessorID="2" KernelTime="315" UserTime="405" />
    <Channel />
    <Computer />
  </System>
  <EventData>
    <Data Name="PartA_PrivTags">16777216</Data>
    <ComplexData Name="wilActivity">
      <!-- Michael: This is 0x80270254 == E_APPLICATION_NOT_REGISTERED
           "This app does not support the contract specified or is not installed." -->
      <Data Name="hresult">2150040148</Data>
      <Data Name="fileName">onecoreuap\base\appmodel\execmodel\modern\activationmanager\extensionhelpers.cpp</Data>
      <Data Name="lineNumber">     221</Data>
      <Data Name="module">activationmanager.dll</Data>
      <Data Name="failureType">       1</Data>
      <Data Name="message"></Data>
      <Data Name="threadId">   11028</Data>
      <Data Name="callContext">\ForegroundActivation</Data>
      <Data Name="originatingContextId">       8</Data>
      <Data Name="originatingContextName">ForegroundActivation</Data>
      <Data Name="originatingContextMessage"></Data>
      <Data Name="currentContextId">       8</Data>
      <Data Name="currentContextName">ForegroundActivation</Data>
      <Data Name="currentContextMessage"></Data>
      <Data Name="failureId">      32</Data>
      <Data Name="failureCount">      32</Data>
      <Data Name="function"></Data>
    </ComplexData>
  </EventData>
  <RenderingInfo Culture="en-US">
    <Task>ActivityError</Task>
  </RenderingInfo>
</Event>
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ActivationManager" Guid="{cf7f94b3-08dc-5257-422f-497d7dc86ab3}" />
    <EventID>0</EventID>
    <Version>0</Version>
    <Level>5</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x0</Keywords>
    <TimeCreated SystemTime="2019-08-18T22:19:27.702384600-07:00" />
    <Execution ProcessID="8272" ThreadID="11028" ProcessorID="2" KernelTime="315" UserTime="405" />
    <Channel />
    <Computer />
  </System>
  <EventData>
    <!-- Michael: This is E_APPLICATION_NOT_REGISTERED
         "This app does not support the contract specified or is not installed." -->
    <Data Name="HRESULT">0x80270254</Data>
    <Data Name="File">onecoreuap\base\appmodel\execmodel\modern\activationmanager\extensionhelpers.cpp</Data>
    <Data Name="Line">     221</Data>
    <Data Name="failure-&gt;pszFunction"></Data>
    <Data Name="failure-&gt;pszMessage"></Data>
    <Data Name="failure-&gt;pszCode"></Data>
    <Data Name="GetCurrentThreadId()">   11028</Data>
    <Data Name="static_cast&lt;DWORD&gt;(failure-&gt;type)">       1</Data>
    <Data Name="failure-&gt;cFailureCount">32</Data>
  </EventData>
  <RenderingInfo Culture="en-US">
    <Task>WIL_Failover</Task>
  </RenderingInfo>
</Event>
Originally created by @metathinker on GitHub (Aug 19, 2019). Originally assigned to: @zadjii-msft on GitHub. <!-- The message here makes the core time sound like a bunch of killjoys. They need to get out more. --> On my computer, the test case file `src\cascadia\LocalTests_TerminalApp\TabTests.cpp` fails to run test setup with the above error message. I'm not sure if this is a general problem or just in my setup, but these tests don't seem to run in Azure DevOps CI ([I checked test run 31597](https://dev.azure.com/ms/Terminal/_build/results?buildId=31597&view=ms.vss-test-web.build-test-results-tab)) so I can't be sure. ### Environment Windows build number: Microsoft Windows [Version 10.0.18362.295] Windows Terminal version: current master commit 734fc1dcc6de4315d4cc91944c5ea83b7b8a7e1a ### Steps to reproduce 1. Checkout the Terminal repo. 1. Run `tools\razzle.cmd & bz rel` to get a successful build. 1. Run: `"%TAEF%" bin\%PLATFORM%\Release\LocalTests_TerminalApp\TerminalApp.LocalTests.dll /name:"TerminalAppLocalTests::TabTests::*"` ### Expected behavior All tests pass. ### Actual behavior The test file does not run at all, with error 0x80270254 == E_APPLICATION_NOT_REGISTERED (lines manually wrapped): ``` X:\> "%TAEF%" bin\x64\Release\LocalTests_TerminalApp\TerminalApp.LocalTests.dll /name:"TerminalAppLocalTests::TabTests::*" Test Authoring and Execution Framework v10.38k for x64 TAEF: Deploying custom AppXManifest... Copying X:\bin\x64\Release\LocalTests_TerminalApp\TerminalApp.LocalTests.AppxManifest.xml to X:\bin\x64\Release\LocalTests_TerminalApp\AppXManifest.xml Warning: TAEF: Using TE.ProcessHost.exe as the Application Executable for UAP tests is deprecated, please consider using TE.ProcessHost.UAP.exe in your custom manifest. Error: TAEF: [HRESULT: 0x80270254] Failed to create the test host process for out of process test execution. (The IApplicationActivationManager:: ActivateApplication call failed while using a default host. TAEF's ETW logs which are gathered with the /enableEtwLogging switch should contain events from relevant providers that may help to diagnose the failure.) StartGroup: TerminalAppLocalTests::TabTests::TryInitXamlIslands EndGroup: TerminalAppLocalTests::TabTests::TryInitXamlIslands [Blocked] StartGroup: TerminalAppLocalTests::TabTests::TryCreateLocalWinRTType EndGroup: TerminalAppLocalTests::TabTests::TryCreateLocalWinRTType [Blocked] StartGroup: TerminalAppLocalTests::TabTests::TryCreateXamlObjects EndGroup: TerminalAppLocalTests::TabTests::TryCreateXamlObjects [Blocked] StartGroup: TerminalAppLocalTests::TabTests::TryCreateTab EndGroup: TerminalAppLocalTests::TabTests::TryCreateTab [Blocked] Summary of TAEF Warnings: Warning: TAEF: Using TE.ProcessHost.exe as the Application Executable for UAP tests is deprecated, please consider using TE.ProcessHost.UAP.exe in your custom manifest. Summary of Errors Outside of Tests: Error: TAEF: [HRESULT: 0x80270254] Failed to create the test host process for out of process test execution. (The IApplicationActivationManager:: ActivateApplication call failed while using a default host. TAEF's ETW logs which are gathered with the /enableEtwLogging switch should contain events from relevant providers that may help to diagnose the failure.) Summary of Non-passing Tests: TerminalAppLocalTests::TabTests::TryInitXamlIslands [Blocked] TerminalAppLocalTests::TabTests::TryCreateLocalWinRTType [Blocked] TerminalAppLocalTests::TabTests::TryCreateXamlObjects [Blocked] TerminalAppLocalTests::TabTests::TryCreateTab [Blocked] Summary: Total=4, Passed=0, Failed=0, Blocked=4, Not Run=0, Skipped=0 ``` Creating the ETW log and parsing it with Windows' built-in `tracerpt.exe` tool yields a number of interesting errors. As best as I can tell from my very limited knowledge, there was a problem with the AppX package extensions (&lt;Extension&gt; elements in AppXManifest.xml). ``` <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="CombaseTraceLoggingProvider" Guid="{1aff6089-e863-4d36-bdfd-3581f07440be}" /> <EventID>0</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x0</Keywords> <TimeCreated SystemTime="2019-08-18T22:19:27.701635500-07:00" /> <Execution ProcessID="8272" ThreadID="11028" ProcessorID="0" KernelTime="315" UserTime="405" /> <Channel /> <Computer /> </System> <EventData> <!-- Michael: This is 0x80040154 == REGDB_E_CLASSNOTREG "Class not registered" --> <Data Name="hresult">-2147221164</Data> <Data Name="code"></Data> <Data Name="message"></Data> <Data Name="function"></Data> <Data Name="fileName">onecore\com\combase\extensioncatalog\extensioncatalog.cpp</Data> <Data Name="lineNumber"> 1215</Data> </EventData> <RenderingInfo Culture="en-US"> <Task>ComError</Task> </RenderingInfo> </Event> [snip snip] <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="ActivationManager" Guid="{cf7f94b3-08dc-5257-422f-497d7dc86ab3}" /> <EventID>0</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x0</Keywords> <TimeCreated SystemTime="2019-08-18T22:19:27.702335700-07:00" /> <Execution ProcessID="8272" ThreadID="11028" ProcessorID="2" KernelTime="315" UserTime="405" /> <Channel /> <Computer /> </System> <EventData> <Data Name="PartA_PrivTags">16777216</Data> <ComplexData Name="wilActivity"> <!-- Michael: This is 0x80270254 == E_APPLICATION_NOT_REGISTERED "This app does not support the contract specified or is not installed." --> <Data Name="hresult">2150040148</Data> <Data Name="fileName">onecoreuap\base\appmodel\execmodel\modern\activationmanager\extensionhelpers.cpp</Data> <Data Name="lineNumber"> 221</Data> <Data Name="module">activationmanager.dll</Data> <Data Name="failureType"> 1</Data> <Data Name="message"></Data> <Data Name="threadId"> 11028</Data> <Data Name="callContext">\ForegroundActivation</Data> <Data Name="originatingContextId"> 8</Data> <Data Name="originatingContextName">ForegroundActivation</Data> <Data Name="originatingContextMessage"></Data> <Data Name="currentContextId"> 8</Data> <Data Name="currentContextName">ForegroundActivation</Data> <Data Name="currentContextMessage"></Data> <Data Name="failureId"> 32</Data> <Data Name="failureCount"> 32</Data> <Data Name="function"></Data> </ComplexData> </EventData> <RenderingInfo Culture="en-US"> <Task>ActivityError</Task> </RenderingInfo> </Event> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="ActivationManager" Guid="{cf7f94b3-08dc-5257-422f-497d7dc86ab3}" /> <EventID>0</EventID> <Version>0</Version> <Level>5</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x0</Keywords> <TimeCreated SystemTime="2019-08-18T22:19:27.702384600-07:00" /> <Execution ProcessID="8272" ThreadID="11028" ProcessorID="2" KernelTime="315" UserTime="405" /> <Channel /> <Computer /> </System> <EventData> <!-- Michael: This is E_APPLICATION_NOT_REGISTERED "This app does not support the contract specified or is not installed." --> <Data Name="HRESULT">0x80270254</Data> <Data Name="File">onecoreuap\base\appmodel\execmodel\modern\activationmanager\extensionhelpers.cpp</Data> <Data Name="Line"> 221</Data> <Data Name="failure-&gt;pszFunction"></Data> <Data Name="failure-&gt;pszMessage"></Data> <Data Name="failure-&gt;pszCode"></Data> <Data Name="GetCurrentThreadId()"> 11028</Data> <Data Name="static_cast&lt;DWORD&gt;(failure-&gt;type)"> 1</Data> <Data Name="failure-&gt;cFailureCount">32</Data> </EventData> <RenderingInfo Culture="en-US"> <Task>WIL_Failover</Task> </RenderingInfo> </Event> ```
claunia commented 2026-01-30 23:22:11 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 19, 2019):

So for the record, these tests are designed to not run in CI. Unfortunately the tests require Windows 1903, and the CI lab machines are all running Server 2019, which is actually 1809 :(.

This is a known issue with the TabTests currently, but I haven't had a chance to dig in deeper. When I wrote them originally, I was under the impression that it was an OS bug. If you could help us figure out why these don't work, I'd officially owe you a beer when I get back to campus :P

@zadjii-msft commented on GitHub (Aug 19, 2019): So for the record, these tests are designed to _not_ run in CI. Unfortunately the tests require Windows 1903, and the CI lab machines are all running Server 2019, which is actually 1809 :(. This is a _known_ issue with the TabTests currently, but I haven't had a chance to dig in deeper. When I wrote them originally, I was under the impression that it was an OS bug. If you could help us figure out _why_ these don't work, I'd officially owe you a beer when I get back to campus :P
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-CodeHealth Help Wanted Issue-Bug Product-Meta Resolution-Fix-Committed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#3474
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?