Skip to content

Let IronPython Compiler only create one exe file when target to exe or winexe #1786

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
wherewhere wants to merge 11 commits into
base: main
Choose a base branch
from

Change MessageBox to Debug

053d7bd
Select commit
Loading
Failed to load commit list.
Open

Let IronPython Compiler only create one exe file when target to exe or winexe #1786

Change MessageBox to Debug
053d7bd
Select commit
Loading
Failed to load commit list.
Azure Pipelines / IronPython3 failed Aug 31, 2025 in 23m 53s

Build #20250831.4 had test failures

7 errors / 11 warnings

Details

Tests

  • Failed: 2 (0.04%)
  • Passed: 2,844 (62.91%)
  • Other: 1,675 (37.05%)
  • Total: 4,521

Annotations

Check failure on line 120 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / IronPython3

Build log #L120 

PowerShell exited with code '1'.

Check failure on line 67 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / IronPython3

Build log #L67 

PowerShell exited with code '1'.

Check failure on line 67 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / IronPython3

Build log #L67 

PowerShell exited with code '1'.

Check failure on line 19581 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / IronPython3

Build log #L19581 

PowerShell exited with code '1'.

Check failure on line 1 in IronPythonTest.Cases.CPythonCases.net8.0.CPython.test_userstring

See this annotation in the file changed.

@azure-pipelines azure-pipelines / IronPython3

IronPythonTest.Cases.CPythonCases.net8.0.CPython.test_userstring 

  Expected: 0
  But was:  1
Raw output 
   at NUnit.Framework.Internal.Commands.TestMethodCommand.Execute(TestExecutionContext context)
   at NUnit.Framework.Internal.Execution.SimpleWorkItem.<>c__DisplayClass4_0.<PerformWork>b__0()
   at NUnit.Framework.Internal.ContextUtils.<>c__DisplayClass1_0`1.<DoIsolated>b__0(Object _)

1)    at NUnit.Framework.Internal.Commands.TestMethodCommand.Execute(TestExecutionContext context)
   at NUnit.Framework.Internal.Execution.SimpleWorkItem.<>c__DisplayClass4_0.<PerformWork>b__0()
   at NUnit.Framework.Internal.ContextUtils.<>c__DisplayClass1_0`1.<DoIsolated>b__0(Object _)

Check failure on line 1 in IronPythonTest.Cases.CPythonCases.net6.0.CPython.test_userstring

See this annotation in the file changed.

@azure-pipelines azure-pipelines / IronPython3

IronPythonTest.Cases.CPythonCases.net6.0.CPython.test_userstring 

  Expected: 0
  But was:  1
Raw output 
   at NUnit.Framework.Internal.Commands.TestMethodCommand.Execute(TestExecutionContext context)
   at NUnit.Framework.Internal.Execution.SimpleWorkItem.<>c__DisplayClass4_0.<PerformWork>b__0()
   at NUnit.Framework.Internal.ContextUtils.<>c__DisplayClass1_0`1.<DoIsolated>b__0(Object _)

1)    at NUnit.Framework.Internal.Commands.TestMethodCommand.Execute(TestExecutionContext context)
   at NUnit.Framework.Internal.Execution.SimpleWorkItem.<>c__DisplayClass4_0.<PerformWork>b__0()
   at NUnit.Framework.Internal.ContextUtils.<>c__DisplayClass1_0`1.<DoIsolated>b__0(Object _)
View more details on Azure Pipelines