search

tlambert03 / napari-plugin-tests

0 stars 0 forks source link

Find alternate strategy for testing napari main #2

Open jni opened 2 years ago

jni commented 2 years ago

@tlambert03 I found this line through code search after @Czaki's post on Zulip:

https://github.com/tlambert03/napari-plugin-tests/blob/114c69ba03e69b05a96ff6bc7b53cdc980cf6625/tox.ini#L34

The actions here aren't running (though I don't understand why), but we should probably remove that line anyway... I don't know how to get tox to work with main without that line though.

tlambert03 commented 2 years ago

The actions here aren't running (though I don't understand why),

actions aren't running here due to inactivity. this is a rather old experiment, that never received much enthusiasm :)

jni commented 2 years ago

I think both Draga and I were very excited! But no, what I mean is, the workflow specifies running every 12h. Did you just disable actions on this repo?

tlambert03 commented 2 years ago

I've taken a few swings at this general concept, each with subtly different repository names :)

This particular one was only ever testing a handful of plugins, and offered a way for plugins to register themselves for tests and tests dependencies (see https://github.com/tlambert03/napari-plugin-tests/blob/main/cases/napari-omero.yml)

later experiments tried to do the whole "test all the things" approach.

This one stopped after 60 days of inactivity:

Untitled