Skip to content

Studio 2026 props #1818

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
FlaviuTritean wants to merge 6 commits into
base: Studio_2026
Choose a base branch
from

Automated - add the .props file to Solutions Root

4e0d1cd
Select commit
Loading
Failed to load commit list.
Open

Studio 2026 props #1818

Automated - add the .props file to Solutions Root
4e0d1cd
Select commit
Loading
Failed to load commit list.
Azure Pipelines / TermExcelerator succeeded Mar 25, 2026 in 3m 46s

Build #20260325.1 had test failures

4 errors / 23 warnings

Details

Tests

  • Failed: 1 (3.45%)
  • Passed: 28 (96.55%)
  • Other: 0 (0.00%)
  • Total: 29

Annotations

Check failure on line 65 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / TermExcelerator

Build log #L65 

[xUnit.net 00:00:05.23]     Sdl.Community.TermExcelerator.Tests.ExcelTerminologyLoaderTests.Get_All_Terms_With_Header(id: 22, expectedSource: "unaccountable", expectedTarget: "unerklärbar|unerfindlich", expectedApproved: "Approved|Not approved", expectedCount: 31) [FAIL]

Check failure on line 108 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / TermExcelerator

Build log #L108 

Test Run Failed.

Check failure on line 127 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / TermExcelerator

Build log #L127 

Error: The process 'D:\a\_tasks\VSTest_ef087383-ee5e-42c7-9a53-ab56c98420f9\2.269.0\Modules\DTAExecutionHost.exe' failed with exit code 1

Check failure on line 128 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / TermExcelerator

Build log #L128 

Vstest failed with error. Check logs for failures. There might be failed tests.

Check failure on line 1 in Sdl.Community.TermExcelerator.Tests.ExcelTerminologyLoaderTests.Get_All_Terms_With_Header(id: 22, expectedSource: "unaccountable", expectedTarget: "unerklärbar|unerfindlich", expectedApproved: "Approved|Not approved", expectedCount: 31)

See this annotation in the file changed.

@azure-pipelines azure-pipelines / TermExcelerator

Sdl.Community.TermExcelerator.Tests.ExcelTerminologyLoaderTests.Get_All_Terms_With_Header(id: 22, expectedSource: "unaccountable", expectedTarget: "unerklärbar|unerfindlich", expectedApproved: "Approved|Not approved", expectedCount: 31) 

Assert.Equal() Failure
          ↓ (pos 0)
Expected: test1
Actual:   unaccountable
          ↑ (pos 0)
Raw output 
   at Sdl.Community.TermExcelerator.Tests.ExcelTerminologyLoaderTests.<Get_All_Terms_With_Header>d__3.MoveNext() in \TermExcelerator\Sdl.Community.TermExcelerator.Tests\ExcelTerminologyLoaderTests.cs:line 70
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
View more details on Azure Pipelines