-
Notifications
You must be signed in to change notification settings - Fork 45
BUG: can't run tests after JSON reporting addition #138
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The pytest-json-report plugin should be required. Are you getting this error with it installed? It's in the requirements.txt With that being said, if this diff makes it optional, I'm fine with that. Also you should only test against tagged releases. I wonder if there's an easy for people to test the "latest" tag without having to manually update it, but also not just always testing master. Maybe we should make a |
Yes, the error shows up with the plug-in installed. I see it in the CI for
this project as well. The diff is needed even with plugin.
…On Thu, Aug 25, 2022 at 16:32 Aaron Meurer ***@***.***> wrote:
The pytest-json-report plugin should be required. Are you getting this
error with it installed? It's in the requirements.txt
With that being said, if this diff makes it optional, I'm fine with that.
Also you should only test against tagged releases. I wonder if there's an
easy for people to test the "latest" tag without having to manually update
it, but also not just always testing master. Maybe we should make a latest
branch which always points to the latest tag, and make that the default
branch. CC @honno <https://github.com/honno>
—
Reply to this email directly, view it on GitHub
<#138 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4JOZTBXVMYKSJE2CXW3TTV27X7NANCNFSM57UOEHMQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Following the merge of gh-131 a few days ago, our testing with the suite here started to fail as described at kokkos/pykokkos#63
I can reproduce in
act
and locally as well:From a quick check, this diff gets rid of the problem, but I'm not sufficiently familiar with the hook side of
pytest
to say if this is what you'd want (and how you'd adjust your CI to catch the original issue).In fact, looking more closely at the merged PR, your CI did fail with the same error we are seeing in
pykokkos
! Should I just pin to a commit for a while or was that accidental?The text was updated successfully, but these errors were encountered: