List of tests in test/unit/test.py is not up to date
List of tests in test/unit/test.py
is not up to date. As a result, some tests, for example refinement/python/refine.py
are not run.
Comments (16)
-
reporter -
reporter Also list of demos not running in parallel in
test/regression/test.py
should be checked as many of them have been fixed but possibly not removed from the list. -
Has this issue be sufficiently resolved for 1.3?
-
reporter -
reporter Ok, this is just a bug in buildbot's Console view where it shows wrong commit hashes and description.
-
reporter - changed status to resolved
-
reporter - changed status to open
-
reporter - changed status to resolved
-
reporter - changed status to open
fix-issue-164 is ready to be merged into master
-
@blechta - The buildbot is configured to only be triggered by commits to master. A commit to next will not trigger the buildbot, so one has to do a forced build to test a commit to next.
-
reporter @johannes_ring Ok. Another issue is that in Console view of next just commit hashes and descriptions from master are shown although actually used commits are from next according to observation of stdout.
-
@blechta you need to click on each buildbot to see what revision is processed. The console view can not show what revision is processed on each buildbot. That will not scale.
With that limitation I think it is fine that it "only" shows whats going on the master buildbot.
-
Sorry just realize you linked to a next dedicated console view. I first thought you meant the full console view. I agree that showing master revisions on the next view is confusing...
-
reporter Ok, I see, @johanhake . You can merge
fix-issue-164
into master in the meanwhile. -
- changed status to resolved
-
- removed milestone
Removing milestone: 1.3 (automated comment)
- Log in to comment
Possibly some more maintainable way of picking tests (e.g. parsing a directory tree like with regression tests) could be added after 1.3 release. This fix could be done within fixing isssue 42.