Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Adds test cases for member changes during a domain reload#1275

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.

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

Already on GitHub?Sign in to your account

Conversation

BadSingleton
Copy link
Contributor

@BadSingletonBadSingleton commentedNov 9, 2020
edited
Loading

The tests are marked as expected failures for now.

What does this implement/fix? Explain your changes.

This adds a test harness/framework for renaming/removing members during domain reload. Actual fixes for these tests will com in other pull request(s).

Does this close any currently open issues?

This will help start addressing#1250

Any other comments?

This supersedes, in part,#1269

Checklist

Check all those that are applicable and complete.

  • Make sure to include one or more tests for your change
  • If an enhancement PR, please create docs and at best an example
  • Add yourself toAUTHORS
  • Updated theCHANGELOG

The tests are marked as expected failures for now.
@dnfadmin
Copy link

dnfadmin commentedNov 9, 2020
edited
Loading

CLA assistant check
All CLA requirements met.

@codecov-io
Copy link

codecov-io commentedNov 9, 2020
edited
Loading

Codecov Report

Merging#1275 (3adc559) intomaster (182faed) willdecrease coverage by3.43%.
The diff coverage isn/a.

Impacted file tree graph

@@            Coverage Diff             @@##           master    #1275      +/-   ##==========================================- Coverage   87.97%   84.53%   -3.44%==========================================  Files           1        1                Lines         291      291              ==========================================- Hits          256      246      -10- Misses         35       45      +10
FlagCoverage Δ
setup_linux59.45% <ø> (-5.85%)⬇️
setup_windows74.22% <ø> (ø)

Flags with carried forward coverage won't be shown.Click here to find out more.

Impacted FilesCoverage Δ
setup.py84.53% <0.00%> (-3.44%)⬇️

Continue to review full report at Codecov.

Legend -Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing data
Powered byCodecov. Last update182faed...3adc559. Read thecomment docs.

@BadSingletonBadSingleton mentioned this pull requestNov 19, 2020
4 tasks
Copy link
Member

@lostmsulostmsu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

What's the status of the time spent running these tests? Are they only enabled for supported configurations?

Comment on lines 51 to 60
<PropertyGroup Condition="$(Configuration.Contains('Debug')) AND '$(TargetFramework)'=='netstandard2.0'">
<DebugSymbols>true</DebugSymbols>
<Optimize>false</Optimize>
<DebugType>full</DebugType>
</PropertyGroup>
<PropertyGroup Condition="$(Configuration.Contains('Release')) AND '$(TargetFramework)'=='netstandard2.0'">
<DebugSymbols>true</DebugSymbols>
<Optimize>true</Optimize>
<DebugType>portable</DebugType>
</PropertyGroup>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

A lot of stuff in this file seems like unnecessary clutter. Can you clean it up?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

It's mostly a copy from another project file. I'll see what I can remove

pythonnet.sln Outdated
Comment on lines 198 to 212
{7539EBD5-7A15-4513-BCB0-1D9BEF112BC2}.DebugWinPY3|x64.Build.0 = DebugWinPY3|x64
{7539EBD5-7A15-4513-BCB0-1D9BEF112BC2}.DebugWinPY3|x86.ActiveCfg = DebugWinPY3|x86
{7539EBD5-7A15-4513-BCB0-1D9BEF112BC2}.DebugWinPY3|x86.Build.0 = DebugWinPY3|x86
{7539EBD5-7A15-4513-BCB0-1D9BEF112BC2}.ReleaseMono|x64.ActiveCfg = ReleaseMono|x64
{7539EBD5-7A15-4513-BCB0-1D9BEF112BC2}.ReleaseMono|x86.ActiveCfg = ReleaseMono|x86
{7539EBD5-7A15-4513-BCB0-1D9BEF112BC2}.ReleaseMonoPY3|x64.ActiveCfg = ReleaseMonoPY3|x64
{7539EBD5-7A15-4513-BCB0-1D9BEF112BC2}.ReleaseMonoPY3|x86.ActiveCfg = ReleaseMonoPY3|x86
{7539EBD5-7A15-4513-BCB0-1D9BEF112BC2}.ReleaseWin|x64.ActiveCfg = ReleaseWin|x64
{7539EBD5-7A15-4513-BCB0-1D9BEF112BC2}.ReleaseWin|x64.Build.0 = ReleaseWin|x64
{7539EBD5-7A15-4513-BCB0-1D9BEF112BC2}.ReleaseWin|x86.ActiveCfg = ReleaseWin|x86
{7539EBD5-7A15-4513-BCB0-1D9BEF112BC2}.ReleaseWin|x86.Build.0 = ReleaseWin|x86
{7539EBD5-7A15-4513-BCB0-1D9BEF112BC2}.ReleaseWinPY3|x64.ActiveCfg = ReleaseWinPY3|x64
{7539EBD5-7A15-4513-BCB0-1D9BEF112BC2}.ReleaseWinPY3|x64.Build.0 = ReleaseWinPY3|x64
{7539EBD5-7A15-4513-BCB0-1D9BEF112BC2}.ReleaseWinPY3|x86.ActiveCfg = ReleaseWinPY3|x86
{7539EBD5-7A15-4513-BCB0-1D9BEF112BC2}.ReleaseWinPY3|x86.Build.0 = ReleaseWinPY3|x86
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Does the new project really need all these configurations? It might just needDebug andRelease. Solution configurations do not have to map 1:1 to project configurations.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Probably not. I think it does require ax86 variant lest thexplat build doesn't run. I'll see what I can remove.

@BadSingleton
Copy link
ContributorAuthor

What's the status of the time spent running these tests? Are they only enabled for supported configurations?

Good question. Each case takes ~2.2 seconds on my machine. Because they run through pytest, I haven't found a way to have them not run in netstandard builds (where the runner code isifdef'd out). The solution might be to move the test harness to a nunit test

@lostmsu
Copy link
Member

Has this been completely superseded by#1287 ?

@BadSingleton
Copy link
ContributorAuthor

Has this been completely superseded by#1287 ?

We can consider it has. The original plan was to have the tests merged in before the fixes, but the fixes requires the tests..

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@lostmsulostmsulostmsu requested changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

4 participants
@BadSingleton@dnfadmin@codecov-io@lostmsu

[8]ページ先頭

©2009-2025 Movatter.jp