Skip to content

Changed wheel name to smlptech#74

Merged
mdmitry1 merged 11 commits intomasterfrom
smlptech
Mar 27, 2026
Merged

Changed wheel name to smlptech#74
mdmitry1 merged 11 commits intomasterfrom
smlptech

Conversation

@mdmitry1
Copy link
Copy Markdown
Collaborator

  1. Changed wheel name to smlptech-1.0.1-cp311-cp311-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl
  2. Rebuilt all three wheel test images
  3. Regression passed for all images

@mdmitry1 mdmitry1 mentioned this pull request Mar 25, 2026
25 tasks
@mdmitry1 mdmitry1 changed the title Changed wheel name to smlp Changed wheel name to smlptech Mar 25, 2026
@mdmitry1 mdmitry1 requested review from fbrausse, konstantin-korovin and zurabksmlp and removed request for zurabksmlp March 26, 2026 04:22
@fbrausse
Copy link
Copy Markdown
Collaborator

I suppose there will be a name conflict with this other smlp package if we keep installing bin/smlp and also with the package name smlp used here

smlp = "smlp.run_smlp:main2"
and in the source files smlp_{optimize,solver,verify,query,terms}.py

@mdmitry1
Copy link
Copy Markdown
Collaborator Author

mdmitry1 commented Mar 26, 2026

I've not seen any conflict, if fresh virtual environment is used.
I run regression and it passed.
In Docker there is also no conflict.

@fbrausse
Copy link
Copy Markdown
Collaborator

You are renaming the wheel due to the name conflict with that other "smlp" package on pypi, yes? As that one provides a Python package called smlp that one can import with import smlp, there is a conflict if we keep our package name smlp as well, is there not?

@mdmitry1
Copy link
Copy Markdown
Collaborator Author

Conflict will occur only if someone needs both smlp packages simultaneously.
I believe that chances for this are slim

@fbrausse
Copy link
Copy Markdown
Collaborator

Why do we need the *.log files in tests/smlp_regression? I particular, since 36 tests seem to have the status "Failed". I think it is better to not have an official reference file that claims that regression tests fail.

Copy link
Copy Markdown
Collaborator

@fbrausse fbrausse left a comment

Choose a reason for hiding this comment

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

Using the two patches mentioned earlier, I am able to build, install and successfully test the smlptech wheel.

However, I would still like to know why this PR includes the *.log files with failed tests. Are they expected to fail?

@fbrausse fbrausse added the release Confirmed to be release related label Mar 26, 2026
@mdmitry1
Copy link
Copy Markdown
Collaborator Author

Hi Franz,

Yes - many tests are expected to fail.
Therefore I'm comparing new failures to the expected.
It can be easily validated by running regression on any of previous tags.
Now we have more failed tests then before as after using pip install order of the attributes in the json file has changed in some tests.
As soon as regression will be cleaned, this won't be necessary.
If I'm not mistaken, regression is supposed to be cleaned before the release.

Dmitry

@fbrausse
Copy link
Copy Markdown
Collaborator

fbrausse commented Mar 26, 2026

Yes - many tests are expected to fail.

I could imagine users trying out SMLP to be surprised by failing tests. Should we document somewhere (in some README, I guess) the reasons for failing tests and which tests are expected to fail?

Now we have more failed tests then before as after using pip install order of the attributes in the json file has changed in some tests.

Indeed, I've also seen this phenomenon. Not sure where it comes from, but for me it's clear: order shouldn't matter in those JSON objects. Similar to many of the lines of log messages: they are not relevant to the exact test result and should be ignored. Some are ignored by the smlp_regr.py script, but that needs to change to a more opt-in approach in my opinion. Line-by-line compatibility is not what we're aiming for with SMLP.

As soon as regression will be cleaned, this won't be necessary.
If I'm not mistaken, regression is supposed to be cleaned before the release.

Maybe I missed this before, what does "cleanup of regression tests" mean? What are the plans here?

@zurabksmlp
Copy link
Copy Markdown
Collaborator

zurabksmlp commented Mar 26, 2026 via email

@mdmitry1
Copy link
Copy Markdown
Collaborator Author

Cleanup of regression tests mean that regression for the released version will pass

Copy link
Copy Markdown
Collaborator

@fbrausse fbrausse left a comment

Choose a reason for hiding this comment

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

Cleanup of regression tests mean that regression for the released version will pass

Short of disabling those tests I don't see how we'll manage that. We can discuss tomorrow or later. For this PR, as we already have some of those logs somehow, it's fine with me.

@mdmitry1 mdmitry1 merged commit 890eebe into master Mar 27, 2026
@mdmitry1 mdmitry1 deleted the smlptech branch March 27, 2026 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release Confirmed to be release related

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants