Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Add flux job submit plumbing command, load new job modules in rc1 #1918
This PR moves
Sharness tests are updated to use one of the two job submission interfaces.
In addition, sharness tests that formerly forced the "none" security mechanism when configured
To make it easier to work with the new
Finally, fix a bug introduced in #1913, which moved the C++ jobspec validator without updating its path in code that checks for its existence used as evidence that
Problem: previous "cleanup" of libjobspec renamed the validator executable, but the ingest sharness test was not updated, so conditional test of invalid jobspec ingest was not running. Change the sharness test to look for the validator executable by its new name.
@@ Coverage Diff @@ ## master #1918 +/- ## ========================================= + Coverage 80.1% 80.1% +<.01% ========================================= Files 195 195 Lines 35109 35080 -29 ========================================= - Hits 28123 28100 -23 + Misses 6986 6980 -6
Problem: the "submitbench" subcommand of flux job does not really belong in a user-facing program. Create a standalone, noinst program that contains the ingest throughput test, then rename flux job submitbench to flux job submit and simplify it so that it only handles one job submission at a time. In flux job submit, if no jobspec argument is present, presume that it should be read from stdin, so "flux job submit" is equivalent to "flux job submit -". Convert sharness tests to call either submitbench or flux job submit as appropriate. Cleanup: now that travis-ci is starting the munge daemon to support the default signing mech in flux-security, there is no need to force all jobs submitted in test to use --sign-type=none when configured with --flux-security.