Just tagging onto this, we'll have a summer intern showing up soon who we
expect to be working on mason improvements (so adding this to the list
isn't necessarily a means of putting it off forever...). If there are
features in mason you'd like to see us get to sooner rather than later,
this would be a good time to weigh in.
Thanks,
-Brad
On Thu, 16 May 2019, Ben Albrecht wrote:
Hi Tim,
You can explicitly include tests via the `tests` field in the
Mason.toml. However, explicitly excluding tests like the .notest feature
is not supported today. I think it'd be reasonable for mason to support
this and have added it to the list of mason to-dos in issue #7106.
Best,
Ben Albrecht Software Engineer | Cray Inc.
[email protected]<mailto:[email protected]> www.cray.com<http://www.cray.com>
________________________________
From: Stavenger, Timothy J via Chapel-developers
<[email protected]>
Sent: Thursday, May 16, 2019 5:49 PM
To: [email protected]
Subject: [Chapel-developers] Does 'mason test' have an equivalent .notest file?
The ‘start_test’ script ignores .chpl files that have a same-named file with
extension .notest:
https://github.com/chapel-lang/chapel/blob/master/doc/rst/developer/bestPractices/TestSystem.rst#controlling-how-it-runs
When I run ‘mason test’ these files are run as tests, so the test build fails.
Is there a similar way to ignore .chpl files for Mason?
Thanks!
Tim
_______________________________________________
Chapel-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-developers
